Home > Visual Studio > Visual Studio 2010 Version Selector Not Working

Visual Studio 2010 Version Selector Not Working

Contents

To have Visual Studio to always open as an administrator, follow @Vdex's instructions. After researching ways to install vsix files manually I could not find a way and then looked into fixing this magical "visual studio version selector". Or if you have the app pinned on your taskbar, you can Ctrl-Shift click it to run as admin. Texas, USA speed ticket as a European citizen, already left the country Let me tell you a little about myself How can I find the perimeter of a concave pentagon? have a peek at this web-site

share|improve this answer edited Jul 29 '10 at 15:04 answered Jul 28 '10 at 14:25 Gene Merlin 76455 that is exactly how i have my environment set up. I'm marking this post as Answered. We recommend upgrading to the latest Safari, Google Chrome, or Firefox. Also, source control providers can make changes to files as they're checked in, so it seems unrealistic to me to have the limitation that solution files shouldn't be modified except by my response

Microsoft Visual Studio Version Selector Location

The BOM was corrupted and the culprit was Textpad. Why do Internet forums tend to prohibit responding to inactive threads? The post describes how to do it for any file type, but I can save you a bit of time by giving you the reg change you need to make (and What Russian letter is this?

  1. I think there is a better way though as we have Win 7 at work which runs as administrator and didn't have this issue.
  2. I did some research online (I can't claim any independent breakthrough here myself) and thought I would collate the various reasons I found why the version selector might not be able
  3. Blog at WordPress.com. %d bloggers like this: David Ebbo Azure Web Sites, Kudu, ASP.NET and random other things about archives tags contact Twitter GitHub RSS Open your solution files as admin
  4. Hope this helps.
  5. If you do the same thing via the Compatability tab, it will set it on the underlying executable, and double clicking solution files won’t work right anymore.
  6. Final note: my reg file above is hard coded to “C:\Program Files (x86)”, which won’t work on all systems so you may need to adjust things.
  7. Browse other questions tagged visual-studio visual-studio-2008 visual-studio-2010 side-by-side or ask your own question.
  8. Can a spellcaster switch between multiple foci?
  9. This was tricky to spot because my diff tool apparently does not even see the BOM share|improve this answer edited Dec 4 '10 at 4:01 answered May 13 '10 at 19:10
  10. However do refer to the solution posted by a_khush_a on the following thread: http://social.msdn.microsoft.com/forums/en-US/vssetup/thread/0e6f4075-aa2e-480c-915f-76286c21f0b4?prof=required He essentially talks about setting the "Run as admin" checkboxes in the compatibilty settings of the VS

Browse other questions tagged visual-studio visual-studio-2008 visual-studio-2005 visual-studio-2010 or ask your own question. share|improve this answer answered Jun 15 '11 at 14:24 David Eison 22326 1 This is gold. After examining the broken solution files and comparing to solution files that worked I found the source of the problem was the UTF8 Byte Order Mark (BOM) at the beginning of Visual Studio Version Selector 2015 If these criteria aren't met, then the Version Selector can't determine which version of Visual Studio to launch.

Canceling setup.'18A project with output type of class library cannot be started directly - with a startup exe26Visual Studio Version Selector Doesn't open17How to downgrade solution from Visual Studio 2010 to I prefer using Notepad++ to add the BOM, but I appreciate the "rawness" of using a hex editor to do this - nice job! How can Average Joe create a micro-state that is a member of the UN in the least amount of time? How can I find the perimeter of a concave pentagon?

Hotels on the Las Vegas strip: is there a commitment to gamble? Vslauncher Location Simple geometry. This problem went away after first going into VS 2008 and using 'Restore File Associations' then right clicking on a 2008 solution file and choosing open with and pointing it to share|improve this answer answered Sep 7 '11 at 20:14 Kelly Cline 1,11611744 add a comment| up vote 1 down vote I had the same problem.

Microsoft Visual Studio Version Selector Download

When I double click to open a project, or click and choose the version selector, or try to change my default application to VS2008's "devenv.exe", no matter what VS2010 just opens. Higher up doesn't carry around their security badge and asks others to let them in. Microsoft Visual Studio Version Selector Location Which security measures make sense for a static web site? Visual Studio Version Selector Wrong Version Thanks a lot. –dyesdyes Jan 19 at 1:31 @JiveDadson In newer VS-es there is the "quick launch" (Ctrl+Q) search/command box, if you type "file associations" it will take you

Seems default values can’t be REG_EXPAND_SZ? http://stickersweb.com/visual-studio/visual-studio-2010-help-not-working.php There are a few other ways you could break it with white-space, but they're the two my source-control seems to like to do. Unix-encoding for your line-terminators? I couldn't quite believe that the line endings would matter, or the encoding, so I had a play around in Notepad++ to verify the above. Visual Studio Version Selector Settings

current community chat Stack Overflow Meta Stack Overflow your communities Sign up or log in to customize your list. Right-click on the shortcut (this works even in the Start Menu) Select "Properties" Select the "Compatibility" tab Click the "Change settings for all users" button at the bottom Enter the administrative Let me know if you know how to do this! http://stickersweb.com/visual-studio/visual-studio-selector-not-working.php Solution File is not UTF-8 Encoded Solution Files must be encoded using UTF-8 and include the BOM at the start (which is EF BB BF).

Secondary menu Skip to primary content Skip to secondary content Search Main menu Skip to primary content Skip to secondary content HomeAbout Post navigation ← Previous Next → Visual Studio 2010 Visual Studio 2015 If you set visual studio (devenv.exe) to always run as administrator, vslauncher won’t be able to run visual studio. First, you try the obvious and right click it, hoping to see the familiar ‘Run As Administrator’ item.

Recent Related Posts Just Installing VS2012 Can Break VS2010 Websites September 3, 2012 Last week, I installed Visual Studio 2012, to play around with new features.

So one should set admin for vslauncher.exe as well as devenv.exe and we are good to go. –Dennis G Dec 2 '12 at 17:04 add a comment| up vote 4 down Call member function template parameter on shared_ptr Moving between attacks with Flying Kick (Unchained Monk) Why did the Winter Soldier kill these characters? Locking plane for a long period My boss asks me to stop writing small functions and do everything in the same loop North by North by North by South East How You signed out in another tab or window.

Should I be concerned about "security"? I guess it is ok as it works and I know i can trust it anyway. –Jonas Stawski Aug 9 '11 at 3:09 add a comment| up vote 0 down vote What specifically did Hillary Clinton say or do, to seem untrustworthy to Americans? have a peek here However, there is one common scenario for which there is no well documented technique: how do you launch a program as admin from a data file?

I'll ask our infrastructure guys how they did it and post back. Friday, July 23, 2010 7:48 PM Reply | Quote Answers 0 Sign in to vote Hi Matt, Thank you for your post in MSDN forum! Very frustrating. The general technique is explained here (thanks to @meligy for pointing me to it).

As it turns out, someone had hand-edited the solution file a few days earlier with an editor that apparently didn't preserve the BOM. I suspect the problem can be traced to a missing UTF-8 Byte Order Mark. (Why VSLauncher is that picky is another question.) ADD: Yes, After opening the new file in a It's maybe worth mentioning that you have to run everything as administrator for it to work (the command prompt and text editor).