Thoughts on Presenting LightSwitch to Professional Developers

Hello LightSwitchers,

It has been a very long time since I have blogged here. I have been dedicating my keystrokes to the book I am writing, LightSwitch in Action, but I am going to try and give my blog some attention (I know, I know, I have said this before).

Since I last wrote here, I have presented LightSwitch to three groups of developers (Pittsburgh .NET Users Group, Hampton Roads .NET User Group, and DevConnections). I have been very pleased that not only have they been very interested, they usually walk away with ideas on what kinds of projects they can use LightSwitch for. So, LightSwitch isn’t just for regular guys like me, experienced coders can benefit from it as well.

I posted more detailed feedback on my corporate blog. Check that out.

Until next time…



Getting the Named Pipes Provider Error 40? Here is an Easy Tip.

Today, I put together a simple reporting application that grabs data from the company’s central database. When I built the application, I got the Named Pipes Provider Error 40. It is a very long winded error that basically says it can’t connect to the local database. Turns out  that the work “local” was key.

Since, I was trying to connect to a remote database, I assumed it was a connection problem between my desktop and that server. I fired up SQL Server Management Studio to test the connection and it worked. So, I scratched my head and went Googling. Most of the results had to do with firewalls and TCP/IP protocols. More head scratching. After a little more Googling, I found a post on MSDN pointing out that LightSwitch needs to connect to the local instance of SQL Express even if you are using remote data (this is the MSDN thread:

A quick check of local SQL Express revealed that the service had been stopped. I started the service and the problem went away.

Here is the easy tip: Read the error message. If it says “local,” it probably means local 😉

Tagged , ,