D'Arcy from Winnipeg
Solution Architecture, Business & Entrepreneurship, Microsoft, and Adoption

Mystery of the Uncooperative VS.NET 2010 Installation SOLVED!

Sunday, March 27, 2011 9:17 PM




Back in August I blogged about an issue I was having with VS.NET 2010. I had installed it on a clean pave of Windows 7 64-bit, but I was getting weird issues with the designer for ASP.NET and I couldn’t add EF files into my projects. The weirdest part was that when I went to the properties of my project, the framework version drop list was empty…no frameworks, 2, 3, 3.5, or 4, were listed!

Now to be sure, my graphics above are tongue in cheek, and the VS.NET team has actually been fantastic in reaching me out and trying to help. A big shout out to Ion Todirel and Kirill Osenkov for the email support and offering various things to try!

Tonight I decided to dedicate some time to trying to get it working. Now, I was a bit predestined to be in software development when my parents decided there should be an apostrophe in my name between the D and the A. I don’t know how many times I’ve been testing code where my name causes the app to blow up. It was a value-add of having me on staff.

So for whatever reason, I thought to myself “Is it something to do with my account name?”, and I created a new account (called it Borg), logged in under it, and tried to start VS.NET. VOILA – NONE of the issues I reported in my blog post!

To test this theory, I created an O’Mally account as well. Logged in, started VS.NET, and BOOM! – all the issues presented themselves!

So the issue has to do with user accounts having apostrophe’s and VS.NET not being able to handle that when navigating system directories to temp file locations.

Now, I should point out that Peter O’Brien actually offered this solution back in December in the comments to my previous blog post, but for whatever reason I never got the email alert and missed having this solved much earlier (Thanks Peter!). However, I think a guy with O’Brien as a name having the same issue and coming to the same conclusion means this is definitely not an isolated issue.



# re: Mystery of the Uncooperative VS.NET 2010 Installation SOLVED!

Saw a similar issue with a guy I worked with when the MSBuild scripts failed - his name had an apostrophe and it broke the build which had worked for months - took them 2-3 weeks to figure that one out. Turned out the folder path was invalid due to the apostrophe - doh! 3/28/2011 2:15 AM | Gregor Suttie

Post a comment