VS2010 contains a ‘setup’ project that creates an installation package.
I need a short cut to the app that will be installed on the user’s desktop. The shortcut I know how to create with the setup/Install is a ‘special’ shortcut and I can’t use it to drop files onto it (and launch the app from it).
Anyone knows how to create a full-features-shortcut that will follow the user’s specified installation path (if he changes it)?
To create a shortcut in a Visual Studio setup project, you can try this:
go to the File System Editor
select "User's Desktop" folder
right-click in the right pane (the files list)
select "Create New Shortcut" context menu item
select the target file when prompted
I'm not sure what you mean by "special shortcut", but this is the only type of shortcut you can create with Visual Studio.
You probably have to disable advertised shortcuts with a tool like Orca. More info here: http://social.msdn.microsoft.com/forums/en-US/winformssetup/thread/d87e8737-dc71-4a5d-a3e7-6653888dd129/?prof=required
Related
I am new to unity platform. I am having visual studio 2008 and unity 3D v4.5.2 working side by side. When ever i create a C# script and opens it to edit, it opens in visual Studio but not in monoDev even i have set the preferences to MonoDev built in and synchronized Assets with MonoDev. but still it opens in VS 2008. All i want is to open in MonoDev but not in VS. Ive searched it but not finding any particular solution to the problem.
Unity Preferences -> External Tools -> External Script Editor and instead of selecting the "Monodevelop (Built In)" option select "Browse" and go select the app exe file yourself and to debug in Monodevelop in Unity 4.3, you need to to tick the options "Development Build", and "Script Debugging" in the Build Settings panel
If you double-click a .cs file in Windows Explorer, does it open Visual Studio? If so, try making the default editor for .cs files the Mono IDE.
Hold Shift, then right-click a .vs file, then pick the "open file with" (or similar) item to permanently assign a new editor to .vs files.
i had the same problem and i broke my head but found the simplest solution
please follow
Open Unity
Go to Edit (Second Tab)
Click on Preferences (A new Tab will open )
Click on External Tools (Second Option Available)
Choose from the list of options Available
AND YOU ARE DONE (Make sure your option of the editor is Installed first LOL)
Click on the "Edit" tab:
Then find "Preference" in the available options. You will find such a mini window opening up, as in the picture below:
Then click on the second option, "External tools":
Then choose from the list of options available (if you have Mono Develop installed then it will be already selected for you)
My suggested options are:
Visual Studio
Mono Develop (usually I have to force close the first time , but I am comfortable with Mono Develop because of its light-weight and powerful performance compared to Visual Studio)
Notepad++ (for the pros)
I have been researching around the web trying to figure out how to add Run As Administrator as the default menu item for a Visual Studio solution when you:
right-click the solution in Windows Explorer
right-click on a pinned application, such as Visual Studio 2013, to bring up the Jump List and then select the solution
The instructions that I have found so far:
http://www.howtogeek.com/howto/windows-vista/add-run-as-administrator-to-any-file-type-in-windows-vista/
show how to easily add the Run As Administrator menu item to an existing file type. You just have to find the right registry keys for the Visual Studio version that you're working with. For example, Visual Studio 2013's registry key for its solution file type is:
[HKEY_CLASSES_ROOT\VisualStudio.sln.12.0]
Then you just copy the Open command under the shell key, then paste it in as a new key whose name is runas.
After that change, when you right-click on the solution in Windows Explorer, Run As Administrator is in the list of commands. But it is not the default.
To open the solution as Administrator from the Jump List menu, when you right-click on Visual Studio as a pinned icon, you have to right-click on the solution file in the Jump List, then select Run As Administrator.
But I couldn't find anywhere about how to make the Run As Administrator the default command in this menu.
So how do you do that?
Easiest way is doing this:
Right click visual studio and open file location.
(If it's the shortcut, right click then click properties. On the bottom click on "Open File Location")
This should lead you to devenv.exe.
Right click this and select troubleshoot compatiblity.
Select troubleshoot program and check off the box for "The program requires additional permissions" and select next.
Now if you open visual studio from where ever, it'll open it as an administrator.
It actually turns out to be one additional registry entry that needs to be set. In the shell key under the file type, change the value of (Default) to be the same name as the command in the registry under the shell folder.
For example, to set Run As Administrator to be the default, you would set the value of (Default) in HKEY_CLASSES_ROOT\VisualStudio.sln.12.0\shell to be runas.
When exported, this setting looks like this:
[HKEY_CLASSES_ROOT\VisualStudio.sln.12.0\shell]
#="runas"
Now when you right-click the solution in Windows Explorer, or when you right-click the solution after right-clicking to bring up the Jump List on the Visual Studio 2013 pinned icon, Run As Administrator is the default command instead of Open.
So you can confidently open the solution itself from Windows Explorer or the Jump List menu and watch as Visual Studio opens as Administrator.
Updating answer for Visual Studio 2015 (under covers version "14.0"). Tested on on Windows 10 Pro v1703 Creators Update. Picture below illustrates the first registry change. Second change goes one better - no need to right-click the jump list item at all.
Windows Registry Editor Version 5.00
;To add "Run As Administrator" to Visual Studio 2015 Taskbar Jump List solution right-clicks
[HKEY_CLASSES_ROOT\VisualStudio.sln.14.0\shell\RunAs]
[HKEY_CLASSES_ROOT\VisualStudio.sln.14.0\shell\RunAs\command]
#="\"C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\Common7\\IDE\\devenv.exe\" \"%1\""
;To make Jump List solutions open As Administrator by default
[HKEY_CLASSES_ROOT\VisualStudio.sln.14.0\shell]
#="runas"
When I right click on a project in the solution explorer I'd like to be able to select an option that would open a new windows "Explorer" that lists the contents of the build directory. I'd settle for the project directory... but getting me into /bin/x86/Debug vs /bin/x86/Release based on the active build configuration would be major bonus.
I find myself manually navigating to that folder fairly often for various reasons - usually on Utility applications which don't have installers / cmd line build scripts etc
I currently use 2005 express. But, am open to upgrading.
A couple things that might be close enough:
add an "external tool" to the Tools menu. In the "Tools | External Tools..." dialog:
Click "Add" and give the new tool whatever name you want
Command: %systemroot%\system32\cmd.exe
Argument: /k "c:\Program Files (x86)\Microsoft Visual Studio 8\VC\vcvarsall.bat" x86
Initial directory: $(TargetDir) // (or whatever appropriate macro)
Right click on a open document's tab and select "Open containing folder"
My VS 2005 Standard IDE already had a "Visual Studio 2005 Command Prompt" tool, but it landed the command window in the VC installation directory. Changing the "Argument" and "Initial directory" fields as above made it land in the project's target directory.
The drawbacks are they don't show up in the right menu for the project and they might not land you exactly where you want, but they should land you pretty close.
No sure this is what you want but the "Open file" icon will pop up a FileOpen dialog in the project folder. From there you can right click the Release or Debug folders to open them in an Explorer (and Cancel the dialog).
I am trying to create an setup project in visual studio 2010 that clears an existing applications program menu. After running the installer that I am creating, the installer duplicated already existing short cuts in the programs menu. I would like to be able to remove all the existing short cuts from a specific programs menu folder and just have the new short cuts appear.
Right click on Deployment project, select properties and set the "RemovePreviousVersion" property to true..
I'm using AnkSVN within Visual Studio 2010, and it covers ~95% of my SVN needs. The biggest missing feature is that I can't find a way to blame a file from directly within VS. The workaround I currently use is to right click on the file within the tablist, and select Open Containing Folder, and then right clicking on the file in Explorer to call Blame.
It's called Annotate in AnhkSVN.
Subversion -> Annotate in the context menu.
I didn't like AnkhSVN's Annotate feature. So I used the following:How to integrate TortoiseSVN into Visual Studio.
Content from above url:
If you're using Visual Studio, you can integrate TortoiseSVN commands to various context menus.
The first step is to add the TortoiseSVN commands as external tools, under the menu TOOLS->External Tools....
Add the name of the command, the path to TortoiseProc.exe and then the parameters for the command.
Use the VS variables wherever needed. Since I add my commands to the context menu of the open file tab, here's the parameters I used:
/command:blame /path:"$(ItemPath)" /line:$(CurLine)
/command:diff /path:"$(ItemPath)"
/command:log /path:"$(ItemPath)"
Notice the /line: parameter: this will make TortoiseBlame automatically scroll to the same line the cursor is located in the opened file in Visual Studio.
Now to add those new commands to the file tab context menu, go to TOOLS->Customize..., select the Commands tab, click the radio button Context menu and then select Other Context Menus | Easy MDI Document Window.
Now you have to select the commands. Problem is that the custom commands are not shown with their title but only as External Command X with X being the number of the external command.
In my case, the commands were number 9-11, you might have to do some trial-and-error here. Just add the commands you think are the ones you added and then check if the right ones show up in the context menu.
NOTE: In Visual Studio 2010 to add a command to the right-click menu of a document’s tab, first you’ll need to right-click on a Visual Studio document tab to work around a Visual Studio bug. (Otherwise the Easy MDI Document Window context menu doesn’t show up in the Customize dialog.) Source