.NET 3.0, SP1 anybody?

[coryking]

Hello, longtime user, first time caller...

Imagine my surprise when my newly minted .NET 3.0 app failed with bizarre run time errors when I ran it on a clean, Windows XP SP2 virtual machine that only had .NET 3.0 from Install Aware. I'd start the application, and it would barf with an "interesting" runtime error that never surfaced on my development machine running Vista. Ever tried debugging a WPF application? I have... it ain't always a straightforward thing to do.

I'll spare you the story, but I'm sure most of you know that Visual Studio 2008 lets you select the .NET runtime to build against. What it does *not* let you select is the specific service pack to build against. Guess what? Apparently
http://msdn.microsoft.com/en-us/library ... rrors.aspx will work just fine on .NET 3.5 and .NET 3.0 SP1, but it will *not* work on plain vanilla .NET 3.0. Since I was compiling my app in Visual Studio 2008 under .NET 3.0, I assumed (rather naievely, I guess) that as long as .NET was on, I was golden.

Since IA does not offer .NET 3.0 SP1, my life is now more complex because I cannot just assume that the .NET 3.0 run time Visual Studio uses is the same as what is installed by IA.

Bottom line? Please, please offer SP1 as a standalone run time and don't bundle it with .NET 3.5. We are writing a consumer application don't want to be the first application they install that upgrades them. We'd rather stick with what we assume most of our customers already have (.NET 3.0).

Thanks!

[Alex_Ronquillo]

Why don't you download the .NET 3.0 SP1 from http://www.microsoft.com/downloads/deta ... laylang=en and install it along with the runtime include it with IA. This will solve your issue.