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

Mystery of the Uncooperative VS.NET 2010 Installation Resolved, or If Life Gives you Lemons…

Thursday, August 26, 2010 10:03 AM




I blogged a few days ago about this maddening issue with VS.NET 2010 and not being able to use the designer for ASP.NET 3.5 projects or add an EF model file to a .NET 4.0 project (You can read all the gory details here). Well my friends, I’m happy to report that I have a solution! Well, not a solution…but a workaround…kinda like how they dumped Megatron into the ocean at the end of Transformers instead of dismantling him: the threat is still there, just dormant.

Unfortunately my workaround doesn’t offer any insight into what the original problem was, but I have a working VS.NET 2010 on my desktop and that’s all that matters. So, what did I do?

- Created a VM
- Installed Windows 7 86x
- Applied all Windows Updates
- Installed VS.NET 2010

Yup. For whatever reason, there are *no* issues installing on the non-64 bit version of Win 7. When I’ve experienced issues with 2010, its always been on the 64 bit OS, so there *must* be something with that combination (although I had a number of peers tell me they were running 2010 on Win7-64 without any issues).

I’m still curious about what the issue might be, but now that I’m at least able to work in the environment I’m relegating it to hobby-interest status.

One thing I definitely want to do is tip my hat and give a big thanks to some Microsofties: Kirill Osenkov and Ion Todirel. When I first tweeted about my issue, Kirill reached out and got me in touch with Ion, who sent me suggestions on things to check and ideas for troubleshooting. Although we didn’t come to a solution, I appreciated that they took time to try and lend a hand, so thanks guys!

If I uncover anything else related to the original problem I’ll post it, but for now…back to jacking Entity Framework into my brain.



No comments posted yet.

Post a comment