When I create a Excel 2010 Add-in project in Visual Studio 2010, and configure my prerequisite publish options for click once deployment, the 'Microsoft Visual Studio 2010 Tools for Office Runtime (x86 and x64) option item, has a warning indicator over the icon, which screen tip says "Prerequisite could not be found for bootstrapping". Once I try to publish, it publishes fine, however, I get the warning:
"Item 'Microsoft.VSTORuntime.4.0' could not be located in 'C:\Program Files\Microsoft SDKs\Windows\v8.0A\Bootstrapper\'."
I've tried re-installing the VSTO 4.0 Runtime to resolve this with no luck. Any ideas how to fix this warning?
Update
After uninstalling VS11, and repairing VS2010, then uninstalling VS2010, and re-installing, I now have these issues:
Have you got Visual Studio 11 installed, bootstrapper should be here
C:\Program Files\Microsoft SDKs\Windows\v7.0A\Bootstrapper
I got VS2010 with Windows 7 ultimate.
Related
I had previously installed WIX 3.8, and could see the "Windows Installer XML" selection when creating a new project in VS 2012. I downloaded and installed VS 2013 Ultimate, with SP1. I did a Repair on WIX, and I did see it referencing VS 2013. But when I go to create a new project in VS 2013, the "Windows Installer XML" does not show.
When I look at C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\Extensions\Microsoft\Wix, it only has a "ProjectTemplates" folder with three zip files in it. The same folder in VS 2012 has a number of items in it.
What do I need to do to correct this (Do the trial versions of VS preclude this from working)?
I had this problem, you cannot do a repair as it won't try to re-detect the VS2013 installation. Just uninstall Wix completely and re-install and it will then work.
I installed the free version of ApexSQL which is awesome in SSMS, but I really don't want all those menus in Visual Studio. I went to add-in manager and unchecked them, but the Startup column is checked and disabled so every time I restart Visual Studio they come back.
Is it possible to permanently remove the ApexSQL menus from Visual Studio?
If you have ApexSql installed and you don't want those pesky menus in Visual Studio do 2 things.
In Visual Studio, go to Tools > Add-in Manager and uncheck the ApexSql addins. Close Visual Studio.
In Windows 7, there's a hidden folder C:\ProgramData. In Windows Explorer go to C:\ProgramData\Microsoft\MSEnvShared\AddIns folder. Edit each of the *.MsvsLoader.Addin files and set <LoadBehavior> to 0. If you can't save the files directly, you'll have to save the files to a different location (desktop maybe) and then copy them back into C:\ProgramData\Microsoft\MSEnvShared\AddIns because there's some Admin privilege required.
Now when you restart VS those ApexSQL menus should be gone
The issue of crowding menus is resolved in latest releases, now all ApexSQL add-ins are under the main ApexSQL menu as sub-menus. They look like this now:
If you don't need ApexSQL add-ins in VS or SSMS you can simply choose not to integrate them with VS or SSMS during the installation, just check out SSMS ot VS version in which you want the add-ins integrated
Note: To get this dialog in which you can check the wanted integration you need to use individual installers not the main one. You can find all individual installers on this link
Disclaimer: I work for ApexSQL as a Support Engineer
For Visual Studio 2010 on Windows 7, I attempted #Chris Bayles suggestion and do not see ApexSql addins under Tools->Add-in Manager.
I followed #Jerome2606's pointer to https://knowledgebase.apexsql.com/remove-add-ins-just-visual-studio-retaining-sql-server-management-studio/ and it worked for me, but only when I removed the parent ApexSQL folder as well.
Summary of what is required to do:
Remove folder
C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\Extensions\ApexSQL
Depending on the version of Visual Studio, the version number in the default installation location will be different:
Product name Version number
Visual Studio 2010 Microsoft Visual Studio 10.0
Visual Studio 2012 Microsoft Visual Studio 11.0
Visual Studio 2013 Microsoft Visual Studio 12.0
Visual Studio 2015 Microsoft Visual Studio 14.0
Select and delete the ApexSQL folder and its contents.
Open Command Prompt as an administrator, then run
"C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\devenv.exe" /setup
Please note the command is different for Visual Studio 2012, 2013, and 2015.
If you are using SSMS v18.0 then you can disable the apex features in following way.
You can find the ApexSQL.Complete.Addin.SSMS18.pkgdef file from following path.
C:\Program Files (x86)\Microsoft SQL Server Management Studio 18\Common7\IDE\Extensions\ApexSQL Complete
Then open this file in Notepad++ Administrator mode and comment the content.
If you need further reading follow this link.
https://knowledgebase.apexsql.com/remove-apexsql-tools-sql-server-management-studio/
I have installed sharepoint 2010 and the sdk, yet I cannot see / open sharepoint projects in Visual Studio. When I go to new >> Project, sharepoint is not anywhere in the options.
If I try and open an event receiver project, I get this project type is not supported in this installation.
I have tried reinstalling the Sharepoint 2010 SDK, and repairing VS 2010 Premium.
Does anyone have any ideas on what I need to do to get this to work?
I'm running VS 2010 Professional and when I ran VS 2010 SP1 it crashed during installation. After that I got the same error message when I opened a solution containing Sharepoint 2010 projects. I tried the following but it didn't solve it:
- Running VS 2010 repair
- Reinstalling VS2010 SP1
- Reinstalling .Net framework 4.0
Same error...
Finally I ran VS2010 setup, 'add remove features', and noticed that the 'Sharepoint Developer Tools' was not included anymore. I added it and now it works!
This was resolved by uninstalling and reinstalling VS 2010 premium. Go Figure!
After installing Visual Studio 2010 Premium and trying to start it, following error message pops up:
Program can't be started, ATL100.dll is missing. Reinstall program to solve the problem.
I searched for the ATL100.dll and found it in:
"C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\redist\ia64\Microsoft.VC100.ATL"
"C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\redist\x64\Microsoft.VC100.ATL"
"C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\redist\x86\Microsoft.VC100.ATL"
Copying the file to "C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE" also won't work.
Any tips how to fix this problem so i can start VS 2010 ?
If ATL stands for "Active Type Library" then it could be some helper DLL for it. Because ATL also is a COM based framework, it could be necessary to register the DLL. Copying would not work in that case.
regsvr32 ATl100.dll
Just a hint for the next time.
FYI,
I had same problem.I couldn't run both Visual Studio 2010 (SP1) and 2012 (U1) due to same error.
I could fix by just repair/reinstalling Visual Studio Service Pack 1.
Here are details.
Repair/Reinstall Visual Studio 2010 -> didn't help
Reinstall Visual Studio 2010 Service Pack 1 -> fixed the problem of VS2010, but VS2012 still had problem
Reinstall Visual Studio 2012 Update 1 -> fixed the problem of VS2012
During no. 3, I couldn't see any GUI. So I just pressed enter key after launch the Update 1 setup.
It'works. I re-reinstalled it and deselected all C++ components during the installation.
I can't publish in 2008, I was previously using 2005 and it published just fine.
Error 2 An error occurred while signing: SignTool.exe not found.
I know there are tons of hits for a search on signtool.exe on google. The ones I've found involve copying the file to X,Y,Z locations and ensuring signtool matches up with your VS command prompt path.
When I run my start-> program files -> visual studio 2008 -> Visual Studio Tools -> Visual Studio Command prompt. and type signtool.exe it finds the file just fine.
I have Visual Studio 2005 professional edition, Visual studio 2008 profession edition,
Visual studio 2005 SDK February 2007, just installed Visial Studio 2008 SDK1.1 to see if that would fix it, no luck.
I have copied signtool.exe to lots of places that were suggested on the google searches, it is now located at all of the following:
C:\Program Files\Visual Studio 2005 SDK\2007.02
C:\Program Files\Microsoft Visual Studio 9.0\Common7\Tools
C:\Program Files\Microsoft Visual Studio 9.0\VB\Bin
C:\WINNT\Microsoft.NET\Framework\v3.5
C:\Program Files\Microsoft SDKs\Windows\v6.0A\Bin
C:\Program Files\Microsoft Visual Studio 8\Common7\Tools\Bin
C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\Bin
C:\Program Files\Microsoft Visual Studio 9.0\SDK\v3.5\Bin
C:\Program Files\Microsoft Visual Studio 9.0\VB\Bin\1033
C:\Program Files\Visual Studio 2005 SDK\2007.02\VisualStudioIntegration\Tools\Bin
I'm on windows XP
2009-06-12 update
I can only publish if I copy signtool.exe to the project folder I'm publishing now.
Replace signtool with "$(FrameworkSDKDir)bin\signtool" with the quotes and see if it works. It tried this now on Visual Studio 2008 Express Edition.
N.B: I have been using same command on VS 2005 for signing the binaries.
This may help some one else....
I got round this problem by going to the signing tab and unchecking the Sign The ClickOnce Manifests option and now it works...
I guess that doesn't FIX the problem..but it gets around it allowing you to publish your application with out the Signtool.exe File.
This may help some one else.... I got round this problem by going to the signing tab and unchecking the Sign The ClickOnce Manifests option and now it works...
that one doesn't worke for me, because every time I uncheck the signing (and save the config) Visual Studio checks it back on.