Larry Smithmier: C# For You (with a side of SQL)

My last post asked about development on Win7 and Vista. I still have tons of complaints about Vista, but I have been developing at home using Win7 exclusively for 3 months now (mainly ASP.NET) and I can’t really complain much anymore. The VS 2008 development of web sites on Win7 is about as painless as it can get. I modified my shortcut for VS to launch as admin, and everything just flows.

I just got the VS 2010 Beta down and I must say, it is quite pretty. I like the new look and feel quite a lot. I am looking forward to putting it through its paces, but I am afraid that most of the really cool new stuff (testing enhancements and such) will have to wait until I get to use it at work. At home, I should probably try the Professional Edition rather than the Ultimate, but I just love the gadgets. I really like the fact that they made Architecture a first class citizen (it has it’s own top level menu structure).

You know it is bad when you find statements like this in a Microsoft document (the emphasis is mine):

Windows XP SP2 and Visual Studio .NET 2005
The recommended development environment for HealthVault applications is Windows XP with Service Pack 2 and Visual Studio .NET 2005. Some of the security settings in this guide are specific to this environment.

Windows Vista and Visual Studio .NET 2008
The HealthVault application environment is fully compatible with Windows Vista. However, Windows Vista locks down many shell and application security settings that are relevant to Web application development. If you choose to develop in Windows Vista, you need to manually configure the Visual Studio development environment to run in Administrator mode. In addition, you will need to take additional steps to configure security settings and grant local user permissions for your application development certificate. Some of those steps may depend on your local environment and are beyond the scope of this document

Signed up for a free account at Beanstalk and am loving what I have seen so far. I like the focus they have and the exposed API to allow mixing their service with another best of breed. They have also done a lot of the interfacing to other services already for you. For now, they are my source control vender of choice. I have started my startup repository and work is underway. Progress has been made and code committed.

Sort of gives me goose bumps. :-)

Add the following line:

ping 127.0.0.1 -n 2 -w 1000 > nul&ping 127.0.0.1 -n 2 -w 1000 > nul

replacing the 2nd 2 with the number of seconds you want to delay.