Created a windows service in VS2012. Right clicked on the service and selected 'Add Installer' as done in VS2010
Got the message:
Unable to add installer. The designer could not add a Project Installer.
Anybody run into this ?
Check to see if the files already exist. In my case, a previous developer excluded the installer files from the project, so I did not see them until I opened a Windows Explorer on the source folder.
Do you have an Express version? I have not run into this problem with Visual Studio Professional 2012 on Windows 8 N Pro. I can right click on the designer surface and click on item "Add Installer" and a class is created called 'ProjectInstaller'.
You can create the project installer class manually. Designers are overrated anyway. I have written a blog article on how to do this.
Simple Installer for Windows Service Using Visual Studio 2012
Is there a reason you need a deployment wizard? Is there a configuration parameter you need to prompt the installing user with? I generally just use a configuration file and package up each environment's configuration with the deployable.
The Project Installer is not included in VS 2012. If you right click your solution and choose Add, New Project, then go to Other Project Types and choose Setup and Deployment, it should take you to the InstallShield page where you can download and install the Limited edition of InstallShield for free (you will have to register and get an activation code via email). Once installed, repeat the steps above and it should prompt you to either register the software or continue with a trial version.
Related
I'm going to create Q# application for the first time. I installed the "Microsoft Quantum Development Kit" and I have .not core 3.1.301 (the latest)
I use VS 2019 Community Edition.
In VS, I see the Q# Application when creating new solution but when I try to create , I get below error:
The project file cannot be opened by the project system, because it is
missing some critical imports or the referenced SDK cannot be found.
Detailed Information: The SDK resolver "NuGetSdkResolver" failed to
run. Unable to find fallback package folder
'C:\Microsoft\Xamarin\NuGet\'.
C:\Program Files\dotnet\sdk\3.1.301\Sdks\Microsoft.Quantum.Sdk\Sdk not
found. Check that a recent enough .NET Core SDK is installed and/or
increase the version specified in global.json.
I could not find any solution over the web.
The Quantum.SDK is not distributed with the extension, instead is downloaded the first time you try to build/create the Q# application.
Looks like Visual Studio is having problems downloading it using NuGet. I can think of two reasons:
1. You are not connected to the internet, so it can't connect to nuget.org to download the package
2. The error points to a missing "C:\Microsoft\Xamarin\NuGet\", I would suggest creating this folder.
I've followed these steps exactly and am getting the error below:
Select File > New > Project...
In the new project window, search for IoT Edge and choose the Azure IoT Edge (Windows amd64) project. Click Next.
In the configure your new project window, rename the project and solution to something descriptive like CSharpTutorialApp. Click Create to create the project.
In the Add Module window, configure your project with the following values:
Select Add to create the module.
I get this error regardless of the combination of solution folders, module names, and any other parameters that I enter during this workflow:
The system cannot find the file specified. (Exception from HRESULT: 0x80070002)
The net result is that no changes are made to the solution -- no IoT Edge module project is created, no other files are altered.
I've tried running Visual Studio 2019 (16.4.3) as administrator, uninstalling and reinstalling the Azure IoT Edge Tools extension, all without success.
What can I do to troubleshoot this further?
Update 1: I've double-checked all documented prerequisites and still have this issue.
Visual Studio 2019 16.4.3, all prerequisite Visual Studio workloads installed
.NET Core workload installed the latest -- 3.1 LTS SDK -- only. Is there a hidden dependency on a specific older .NET Core 2.x SDK somewhere? Or is the documentation for VS Code on the subject out of date? (I'm using VS but was looking everywhere to see if I had missed anything)
Git for Windows installed (via Visual Studio Installer)
Docker Windows Desktop installed & switched to Windows containers
Azure IoT Edge Tools for VS 2019 installed (and uninstalled & reinstalled)
no UNC/FQ paths in the item or project template locations:
C:\Users\larsk\OneDrive\Documents\Visual Studio 2019\Templates\ProjectTemplates
C:\Users\larsk\OneDrive\Documents\Visual Studio 2019\Templates\ItemTemplates
multiple reboots
this is on a machine that just recently got the latest (1909) version of Win10 Pro reinstalled on it.
Update 2: Updating to Visual Studio 2019 16.4.4 did not help either.
The solution turned out to be running a Repair operation through the Visual Studio Installer.
i created a windows form application in VS2010 using QBSDK.
my problem is that the target has QB installed and running, but i get an error when trying to deploy my one-click application. (the error is just that the application generated an error - and i cannot find the log file to see what actually happened).
to solve it, If i install the QBSDK onto the target machine, it runs fine.
My question is:
what do i need to include in my deployment so i DONT have to install the SDK?
You need to install the SDK redistributable components for any application that uses the SDK to work. If you are using QBFC, RDS or the QBO connector, there are only two supported ways to distribute these components:
1. You can use the stand-alone compressed-image installers that Intuit provides.
2. You can use the merge modules that Intuit provides.
I don't use ClickOnce deployment, but I think that if you are using ClickOnce deployment you can not include merge modules. I think there's a way to create a custom prerequisite that will install using the stand alone installer; http://msdn.microsoft.com/en-us/library/ms165429%28VS.80%29.aspx
If you don't want to go that route, you would need to use another deployment option. In Visual Studio 2010, you can create a Visual Studio Installer Setup Project that you can add the merge modules into. This project type is NOT available in the Express editions of Visual Studio, though.
There is a section in the QBSDK Programmer's Guide that gives some more details about deploying the SDK with your application.
I have downloaded and installed all of the prerequisites for using MVC 4 with VS2010. The VS2010 SP1 update, ASP.NET MVC 4 for VS2010, SSDT for VS2010, and LocalDB. When I go to create a new website in VS2010, there should be an "ASP.NET MVC 4 Web Application" template, but there is not. How can I get the templates so I can start a new MVC 4 website in Visual Studio 2010?
Have you tried reinstalling the templates. Follow these directions.
http://msdn.microsoft.com/en-us/library/vstudio/ms247116(v=vs.100).aspx
short answer, open up visual studio command prompt and type:
devenv /installvstemplates
That should restore all your templates.
Check if Project Templates are installed:
Manually search if you find the project template (it would be *.zip) inside %ProgramFiles%\Microsoft Visual Studio 10.0\Common7\IDE\ProjectTemplates\CSharp\Web\1033
If YES, please run devenv.exe /installvstemplates
If NO, then its guaranteed that the ProjectTemplates are not installed. You would have to reinstall to get the ProjectTemplates on your disk.
For the records:
All the installed project templates are available here: (this is the default path)
%ProgramFiles%\Microsoft Visual Studio
10.0\Common7\IDE\ProjectTemplates
This is where the File->New ->Project Dialog loads ProjectTemplates from, and is displayed in the Same Folder heirarchy convention.
You could add another path by updating
Tools -> Options -> Projects and Solutions -> General -> User Project
Template Location
On studio(devenv.exe) launch/loading it would try to create a ProjectTemplateCache on localappdata or %ProgramFiles% based on whether you are local user or admin.
The cache inside Programfiles are available here
%ProgramFiles%\Microsoft Visual Studio
10.0\Common7\IDE\ProjectTemplatesCache
This ProjectTemplateCache directory is Created (if doesnt exists) or Updated(if already exists) by running *devenv.exe /installvstemplates on cmd. This command is run during installation of Visual Studio. Ideally all other installers who ship project templates should run this command. But, sometimes this might fail due to access rights. So its is safe to run it again manually.
See this question
If you didn't install the Visual Web Developer component, the ASP.NET
project templates won't be fully installed. Naturally, because the
installer then thinks it doesn't need to put them there as ASP.NET is
a web development framework.
1) Install it as Administrator. right click on file and run it as Administrator.
2) Uninstall it and Install it as administrator again could solve your problem
If the install went through fine without errors/warnings/exceptions -
Try changing the .NET framework on the New Project window, make sure you are viewing .NET framework 4.0 templates.
PL
Repair MVC 4 installation. It will take care of project template installation
Same as me.
make sure register and activation vs2010 product.if vs not register and not type any key for activation vs You can not ins mvc4 for it.
Please register vs2010 and re-install mvc4.then you can see mvc4 when you create project.
Does anyone use Specflow 1.7.0 with Visual Studio Team System 2008? There are no Specflow templates available in “Add New Item” window after installation.
Installed previous version 1.6.1 and this time integration works fine. Any idea?
I have the same problem.
I was thinking it was because of a bad update of the msi version... but no.
Now : I need to create manually a .feature file
edit :
I have installed cuke4vs
https://github.com/henritersteeg/cuke4vs/downloads
now it's possible to to add features with "Add New Item"
(and in addition the feature file is colored :) )
Most probably found the bug.
Install the next nightly build from build.specflow.org, I hope it will work then.