I have created an application in C# visual studio 2010.
The application works fine in debug mode and builds successfully. The application has three aspects to the solution. When i build and deploy the setup file i get an error on the install as soon as i click install in the steps.
The error says Installation Incomplete, The installer was interuppted before InvoiceProcess could be installed. You need to restart the installer to try again.
When i restart i get the same error.
Both the development machine and machine to deploy on are both 64 bit windows 10.
What could be causing this?
One of the possible reasons that it is not getting installed because IIS6 management compatibility is not configured on IIS.
Visual Studio 2010 installer still targets the older version of IIS (means IIS6) although IIS7 was publicly available in 2008. That’s why IIS6 compatibility is required.
Related
I'm working in a solution that has several .net core (as well as standard and framework) projects.
Up until this morning, when I debugged a .net core project it would launch fine. This morning, that broke. I get an error stating
The library hostfxr.dll was found , but loading it from XXX failed
When I build the project, and try running the EXE, the same thing
happens.
When I add a new project to the solution, it works fine.
When running the built debug version on another machine (with the
.net core SDKs), I get the same issue
When I change the project to
run in Release, it works fine.
When I change the project to run in Debug, and 32bit, it works fine
When I build the project via cli/dotnet build -c Debug, it works.
When I build the project via Visual Studio, in Debug, in 32bit it works.
When I build the project via Visual Studio, in Debug, in 64bit it doesn't work.
I've cleaned/rebuild the project.
I've restarted
I've updated my Visual Studio
I've removed and reinstalled the .net core SDK
Any suggestions on what happened and how I can fix it?
Im running Windows 10 and Visual Studio 2019
UPDATE
After performing my Windows updates overnight, it no longer works when I use dotnet build.
So it turns out that a clean/rebuild doesnt completely clean the solution.
After I deleted the obj and bin folders, and restarted VS, the problem was resolved.
In our case (with a build server on Windows Server 2019), it was a case of user rights.
The user that executed the build process (Jenkins), did have access to the folder where hostfxr.dll was located, but required to be an administrator on the build server.
Test the process running under the name of an admin, before re-installing frameworks or installing any Windows Updates.
I have the latest VS2017 Enterprise.
I have 'ASP.NET and web development' workload installed.
Also I have .NET Core SDK both versions 32/64 bits.
I create new ASP.NET Core Web Application from template.
When I try to 'Start without debugging' I got an error - "The Project doesn't know how to run the profile IIS Express"
At the same time this project can be run successfully from command line
dotnet run
I know that similar question exists but all suggestions from it are not helpful in my case
Visual Studio 2015 can't start IIS Express
I reinstalled my VS from scratch and now it works
try to remove the vs folder and try to run the project
The .vs is a hidden folder so you have to enable the Show hidden files
PS: close visual studio before removing the folder
Windows 10 x64
Visual Studio 2012 x32
.NET Framework 3.5 and 4.6
I cannot run/debug/F5 any projects in Visual Studio. I have tried nopCommerce, BlogEngineDotNet, File->New Website, etc. First I was getting an error about .NET 4.5 and .NET 4.0 not being registered, but I installed the fix from Microsoft (https://support.microsoft.com/en-us/kb/3002339) which resolved that issue.
Now, everytime I try to F5 I get the error below.
I've searched until I was ready to beat my head against the desk. I found a lot of posts from a few years ago saying to use dependency walker to see if any pre reqs fail, but dependency walker says its only good up to Windows 8.
I ran into this issue after I switched the "Default terminal application" to Windows Terminal. I had to restart Visual Studio and then it worked again but using Windows Terminal caused other issues so I had to revert and restart VS again.
As #Trout.Z mentioned, you may also want to enable the Automatically close the console when debugging stops option in Visual Studio. You can find it in the options under Debugging > General.
uninstall Visual Studio 2012 x32 and install new Visual Studio 2012 x64 because your os is 64 bit
above code helps you to make it working.
Under cloud I only see "Get Windows Azure SDK for .NET" yet I know it's installed. The installer sees it.
I should mention I have Visual Studio 2010 installed along size 2012. 2010 has all the project types and works great.
Open Programs and Features, locate the 'Windows Azure Tools for Microsoft Visual Studio 20xx' (where xx is the version of Visual Studio you are experiencing the issue with)
Right click and choose Repair.
Once the repair is complete, re-open Visual Studio, search installed templates for 'Cloud' and the 'Windows Azure Cloud Service' project should appear, confirming that the issue is resolved.
I had this same problem. Rebooted, still couldn't get it to recognize the Azure SDK 2.1 for VS 2012.
When I right-clicked, I only had the options to Uninstall or Change. I chose Uninstall, and another windows popped up asking if I wanted to repair. I chose Repair and then finally Windows Azure Cloud Service appeared.
I've had similar issue few days ago. Both, VS10 and VS12 installed on Win 7 machine. And VC12 didn't see azure so I followed steps from VS12 and installed it again and then it still didn't work.
However, after VS12 and system restart it actually worked.
Have a project that was created in Visual Studio 2008 and deployed to a 64-bit Windows 2003 server. This application references a 32-bit Interop.ActiveDs.dll. The applications were originally compiled for 'Any CPU', however, explicitly compiling as 'x86' doesn't solve the problem. The project targets the 3.5 framework.
The server is running IIS 6.0 in 64-bit mode. When we deploy the version compiled in Visual Studio 2008, the app runs perfectly fine; all pages show up. In retrospect, this is actually surprising.
We migrated the application to Visual Studio 2010 (we did not change the targeted framework) and redeployed. Now we get a BadImageFormatException loading Interop.ActiveDs.dll. Which actually makes more sense than the 2008 version running.
To solve the problem, we set Enable32bitAppOnWin64 to true and ran aspnet_regiis.exe -i from the 32-bit folder of the 2.0 framework (as per various instructions on the web). In IIS, web service extensions, there were two versions of ASP.NET 2.0, one for 32-bit and one for 64-bit. We prohibited the 64-bit version, restarted IIS, and launched the website.
What we expected: The app to run as 32-bit, load the interop, and display
What we got: "Service Unavailable"
All other web pages that were previously working displayed the same message, as did the Visual Studio 2008 version.
The support page here describes the problem exactly, but tells us to do exactly what we did to resolve the problem (enable 32-bit mode).
We've rolled back to 64-bit mode in IIS and deployed the Visual Studio 2008 version for now, but we really need to figure out how to make this app run and load the interop (there are also 32-bit Oracle DLLs that are referenced)
Two questions:
Why does the Visual Studio 2008 version work at all??
How do we get the Visual Studio 2010 version to work? And what is 2010 doing differently that causes the issue?
Thanks in advance!
James
This can happen if you have one DLL compiled for 64-bit and another in 32-bit. Check through all of your references and look for those that do not have 64-bit versions. If you can't find 64-bit versions of your incompatible DLLs, you will need to compile in 32-bit mode.