I've installed the protobuf-net ProtoBufTool custom tool into visual studio to automatically generate .cs file from protocol buffers files. I want to be able to build my project using msbuild for continuous integration and have moved over to using a python script to generate the files.
So how do you remove a custom tool from visual studio?
I've removed it from Documents\Visual Studio 2010\Templates\ItemTemplates\Visual C# which is where I installed it. I've searched for it in the registry and the GAC. I've tried removing it from the file properties in VS and it keeps coming back. I don't want to nuke my machine from orbit!
Edit: I've found the correct registry key now to disable the tool (see Clearing Custom Tool file property in Visual Studio 2010) but I'd still be interested to know if there's a better workflow for managing custom tools
May be you can try:
Tools -> Add-in Managers
Tools -> Extension Manager
"Tools -> External tools" menu can help you.
As Marc pointed out there's a perfectly good uninstaller for just this situation.
Related
I have some merge module projects created using advanced installer. I need to integrate them with visual studio. I have done same for MSI projects and they work fine. but I don't know how to achieve continuous integration for MSM using Visual Studio.
Advanced Installer extension for Microsoft Visual Studio allows to create Advanced Installer Projects for Visual Studio. Each such project is a container that can include a single .AIP file.
The Visual Studio Solution can include one or more Advanced Installer Project for Visual Studio, in accordance with your needs.
Note that you need to remove the default project that is created when adding a new Installer Project to the .sln and add the existing project, the project that builds the .msm package.
edit
Indeed, you are right. It was a misunderstanding on our end.
On my machine I have several extensions installed side by side. One of these extensions also supports the build of a merge module project type.
We do not officially support this yet. The option to build other project types (e.g. Merge Module Project, Updates Configuration Project) with our VS extension will be available in a future version of Advanced Installer. I will let you know when we will add support for this.
Until then, you can use a build event as a workaround to build the Merge Module Project within the Visual Studio project.
To build the .msm project you can use a command line as described below:
http://www.advancedinstaller.com/user-guide/command-line.html#build-project
The command line can be something as below:
AdvancedInstaller.com" /build "$(SolutionDir)Merge module sample.aip"
We're working in quite a large project and is having a hard time getting people to configure their Visual Studio correct (tabs instead of spaces etc.). We found a great solution in using the EditorConfig extension for Visual Studio.
However there are still some developers that seems to ignore our request to install this extension to their Visual Studio and hence I'm wondering if there is any way to force an extension to be installed before a solution can be opened, maybe some setting in the .sln file?
No there is no such option built-in. If your machines are domain joined, you could push out the installer through System Center or domain logon scripts.
You could cheat and create a solution level pre-build step. Create a target file named: before.{solutionname.sln}.targets and store it next to your solution file. Check it into source control. In the targets file you can use standard MsBuild to see if the extension is installed (you'll need to check the file system probably) and if not present force the installation by calling vsixinstaller.exe to trigger the install.
I just started learning unity and I created a project. But my project doesn't have a sln file included in. Every time I create a C# script and open it in Xamarin Studio I can't have any intellisense.
Is it normal not to have sln file in unity project?
If not, how can I add solution file to project?
Why that happened?
If "Open C# Project" doesnt create the .sln file, try updating your external tools first.
In Unity, go to Edit > Preferences, and make sure that Visual Studio is selected as your preferred external editor.
This created the sln file for me.
I finally found the answer.
I closed Xamarin and inside Unity went Assets > Sync MonoDevelop Project Doing this created the two .sln projects: -csharp.sln and .sln
For people looking for answers on newer versions of Unity you may have to build your C# project.
To do this go into File > Build Settings then select the option Create Visual Studio Solution. Then build that and your file explorer will ask you for which folder you want your visual studio solution to be placed into. Then Visual Studio should behave correctly.
For people looking for answers on newer versions of Unity you may have to build your C# project.
First install windows build also in unity hub then select target platform to windows. and now you can see visual studio solution checkbox.
To do this go into File > Build Settings then select the option Create Visual Studio Solution. Then build that and your file explorer will ask you for which folder you want your visual studio solution to be placed into. Then Visual Studio should behave correctly.
Like the post by SSchmid suggests, go into preferences and have Visual Studio as your preferred editor.
I was having a sync issue and the Solution wasn't showing the name of the unity project, ultimately interrupting intellisence.
Found in my settings that the code editor was set to General and not Visual Studio specifically.
Setting it to VS solved it for me.
A screenshot to help those who are too lazy to read.
When I add a reference in a Visual Studio 2010 project via NuGet for Specflow 1.9, I cannot add any features no matter what I do. I've restarted VS, restarted my PC, created new projects, etc. Nothing I do allows me to actually use SpecFlow. I.e. when I go to Project > Add New Item, I do not see any SpecFlow files in the Add New Item dialog.
It is worth noting that I do not have the "ItemTemplates" directory that should supposedly exist in the
"C:\Program Files (x86)\TechTalk\SpecFlow\" directory.
It is also worth noting that I had Visual Studio 2012 Web Express installed, but I'm not sure why that would prevent feature files from showing up under Add > New Item in a VS 2010 project!
Any help is much appreciated.
You need to also install SpecFlow via the Visual Studio Extension Manager.
Tools > Extension Manager
Installing via Nuget only gives you the reference to the SpecFlow dlls - it doesn't install the files for feature templates etc into Visual Studio.
Try to install SpecFlow using Package Manager Console like
PM> Install-Package SpecFlow
More about Package Manager Console
Just to add to ngm's answer.
The NuGet package gives you everything you need to run SpecFlow, for example on a build server.
The VSIX gives you what you need to edit scenarios.
If I'm not mistaken, I got both SpecFlow scenario creation and running of NUnit-based tests working after installing both SpecFlow AND NUnit packages, both via NuGet and also via "Tools > Extension Manager" menu. Until I installed NUnit via "Tools > Extension Manager" I was unable to see execution and reports of any tests/scenarios.
For VS 2013, after I added SpecFlow via nuget, I wasn't able to see the templates as well. I fixed this by:
Downloading a file from
SpecFlow for Visual Studio 2013.
Click Download.
After you download the file (e.g. TechTalk.SpecFlow.Vs2013Integration.vsix), double click it and it will start the installation process.
Close VS 2013. After you start it back up again, you'll be able to see the templates.
Hope this might help other folks too.
After using the package manager to install the .dlls, you need to use tools->"Add-in Manager" to add in the Specflow templates.
i want to make a uninstall option in my C# program?
can u help for this?
and provide some code also
If you deploy your application via a Visual Studio Setup and Deployment Project, an uninstaller will come standard with the installation. It will be available in the Add/Remove Programs of the control panel.
You can create an installation project which will automatically add support for uninstallation. Under Other Project Types you have Setup and Deployment. There is InstallShield LE and Visual Studio Installer. If you choose Setup Project under Visual Studio Installer project, you will have uninstall as part of the built project.
see this video
http://www.youtube.com/watch?v=Z-xFLltALg0
If you want the executable to remove itself. aka self-destruct. Check out this blog http://blog.pedroliska.com/2010/05/20/c-self-destruct-windows-app/