I have been with VS2012 for a few years now. I developed my first asp.net/angularjs project under VS2012.
Secondly, I recently checked out a VS2013 project (written by a 3rd party) which ran just fine under 2012.
Then it was suggested that I install VS2015 on my laptop. This is when things went wrong.
Problems:
I attempted to load the new VS2013 project in VS2015, but it immediately failed to load.
VS2015 error:
Creation of the virtual directory http://localhost:32999/
failed with the error: Filename: redirection.config
Error: Cannot read configuration file
Now when I go back to VS2012 and load my original asp.net/angular project, I get this error:
So in the end, I can't load any projects at all ! Neither 2012 nor 2015.
My local IIS websites are still running fine, by the way, but not the local dev environments.
How can I fix these virtual directories ?
Thanks in advance,
Bob
As per some guidance from this post - IISExpress 8 Cannot read configuration file redirection.config, here's how I got my VS2015 to load up successfully:
Close VS2015
Go into folder %userprofile%\Documents\IISExpress\config
Rename applicationhost.config
Restart VS and load the solution/project
VS should have recreated applicationhost.config, and project should load
Of course, I now have a different error, which I will post anew:
[BadImageFormatException: Could not load file or assembly 'MyWebApp.DAL'
or one of its dependencies. An attempt was made
to load a program with an incorrect format.]
I resolved the same problem by starting visual studio with Administrator rights. This post pointed me in the right direction and gives more solutions.
This may be due to checked-in applicationhost file.
Delete the file from the repository. Build the project again. This file will be created automatically. Don't check in this config file again.
This won't work for everyone, but in my case, the file that couldn't be written was actually a temp file in C:\users\\AppData\Local\Temp\iisexpress. We were getting a company wide virus attack and they shut this area down for everyone. They were able to change the policy just for me and that fixed it.
Related
Update: this bug has been fixed for a while now
I installed Visual Studio 2017.3 yesterday and was trying to used the new Development time IIS Support feature. I think I encountered a bug, and I was wondering if anyone knows a workaround this bug. When I used it with a new project it works fine most of the time. By most of the time, is that I think it is broken sometimes depending on the where the project is located/state of cached data, etc.
Sometimes I get an error "Value cannot be null. Parameter name: name". That's the entire error. No log files, no extra information.
I tried to enable the feature for an existing project I am working
on, it got that error.
I tried adding a new web project in a new solution it worked fine. I tried adding a new web project in the same solution as my project, it didn't work.
I deleted all temp files, all bin obj and .vs folders and .user files in the
solution. Same problem.
I deleted temp folder, visual studio user profile data, and restarted the PC same problem.
I tried again in the same solution with the project not having '.' in the name, it worked.
I did some modification to the project that was working and tried to launch again I got same error.
I reverted all changes so that the project was back to the "empty project" state, still same error.
I removed the project. Exited visual studio, deleted all temp/.vs/.use/bin/obj files. Then restarted and added the project again, it worked.
I restarted VS and tried to relaunch it didn't work.
The aspnet core version seems to be not related to the bug. I had the problem with projects targeting 1.1 and 2.0 and also had the feature working for both versions.
So obviously this is a bug in VS2017.3. Since even if I am doing something wrong I should at least get an error explaining what I do wrong not an ArgumentNullException message. I already made a bug report. I am wondering if someone knows a workaround thing bug.
Thanks a lot in advance.
Update: This bug has been fixed for a while now.
After some investigation and with help from a helpful member of Microsoft's Visual Studio Team, I found that Visual Studio was failing at the point where it grants folder read access to the IIS App Pool account. The method that gets the App Pool account name was returning null, and when that null value was passed to the System.Security.Principal.NTAccount class constructor, the ArgumentNullException is thrown.
A workaround that fixed the problem for me, was changing the App Pool to any other App Pool, trying to launch, then changing it back to the original/desired App Pool.
First You Must Update Visual studio with visual studio Installer and Launch the Visual Studio installer.
And Select the Development time IIS support component and Modify.
Wait For Download is Processing
The component is listed as optional in the Summary panel for the ASP.NET and web development workload.
Then you Create New Project Again
Problem Solved.
I can't load the project in visual studio 2013.
error : The Web project 'ProjectName' is configured to use IIS Express. You must download and install IIS Express in order to load this project.
has any simple solution for this?
I had the same issue with a project on VS2015.
I deleted all the files in the repository (using Windows Explorer), then pulled the branch again, discarding all changes. This solved the issue, so I think this might have been down to some configuration file in the bin or something.
I just downloaded and installed Visual studio on my computer (windows 8.1) to start building windows 8 apps. The problem is when I try to run any application this error message shows up (the application from this error message is called Parcels.comStarter):
Error 1 Error : DEP0700 : Registration of the app failed. Deployment
Register operation on Package
a783768f-d79c-495b-bf64-e59e4297fb42_1.0.0.0_neutral__1mfyfctfxa0tr
from:
(d:\Gebruikers\wardv_000\Downloads\Parcels.comStarter\Parcels.comStarter\Parcels.com\bin\Debug\AppX\AppxManifest.xml)
failed with error 0x8E5E0530. See
http://go.microsoft.com/fwlink/?LinkId=235160 for help diagnosing app
deployment issues. (0x80073cf9) Parcels.com
I searched the entire internet but I didn't found a solution. I also did reinstall visual studio and I still have the problem.
Thanks in advance
Open the Services management console (services.msc) and stop the Windows Installer service.
In Windows Explorer, go to C:\ProgramData\Microsoft\Windows\AppRepository\ and rename PackageRepository.edb to PackageRepository.edb.backup.
Back in the management console, restart the Windows Installer service.
Now run Visual Studio as an administrator and open your project.
I was having this exact same problem, and the solution for me was to unlink my Windows account from my Microsoft account.
There are a couple of things to try.
Run WSReset (press [Win] then type wsreset)
Delete the metastore and remotemetastore folder here: C:\Users\%userprofile%\AppData\Local\Microsoft\Windows\SettingSync where %userprofile% is your username. (I suggest just renaming them to metastore.old and remotemetastore.old)
Make sure that there are no staged packages for the app in question.
If you re-deployed an app that was already installed by some other user, then you would get a deployment error. This should wear off if you change the identity in your package.appxmanifest fie.
You should try an OS refresh. You should not lose your apps and settings.
After that re-link your windows account to microsoft account.
If that doesnt work...The problem may be that visual studio is not able to delete the application data in local folder. So when you go in the location C:\Users\UserName\AppData\Local\Packages you will find application data of app installed in your computer, now you need to find your app's application data and delete the folder. The folder name is the same as the package family name which you can see in your solution.
now again open the solution and rebuild and your app will run. (hopefully)
close visual studio and simulator before deleting the folder.
make sure that your account is set as administrator.
I had the same problem with visual studio running under Parallels VM. The solution was to copy the project from a cloud based directory to a local directory.
It has been a while since I've published my app to Azure. During that time frame, I've upgraded my system from 32-bit to 64-bit meaning a fresh install of Windows and Visual Studio. And Visual Studio Update 3 came out and was applied. When I went to publish an update today, I received the following:
The following exception was thrown trying to publish: Root element is missing.
My web.config file looks fine so I don't think it's this issue.
The app works fine in debug mode so I don't think it's any of the .lsml files as is mentioned here.
And I tried this procedure to hand edit the .ls3proj file but it didn't seem to help.
I previously had an issue trying to publish when I upgraded from the standalone LightSwitch 2011 to Visual Studio 2012. I was able to overcome that issue using the method described in this thread.
Attempting to use this same method resulted in my new project has a full screen error saying "There are critical errors in the application definition metadata..." and 210 individual errors (max errors reached).
The first error, "Cannot create unknown type '{http://schemas.microsoft.com/LightSwitch/2010/xaml/model}GlobalAttributeGroup'." Doesn't make sense because that line in the .lsml is identical from the old project to the new project.
The second error, "Could not find any application definition in the project." Which I do not understand at all.
I am able to publish a simple "Hello, world" style app to my Azure account.
What could be causing this? How can I get more information about exactly which element is causing the issue? The log produced by running devenv /log was not helpful.
Matt Thalman was able to solve my problem over in the Microsoft Forums. The ServiceConfiguration.cscfg and ServiceDefinition.csdef were missing from the project when checked out of version control. Copying those over from a new project restored my ability to publish.
Am trying to Deploy my visual studio 2012 vc++ application through Install Shield wizard.
The error am getting is :
Error 1324. The path .. contains an invalid character
I followed this tutorial and got succeed with a sample application .
http://www.flexerasoftware.com/webdocuments/productdemos/IS2010_VSLE_Demo/IS2010_VSLE_Demo-lite.html
But when i try to deploy my application, the setup file which i created is giving me this error.
Please help me
I've never seen this one before in the wild but it's described at:
http://support.microsoft.com/kb/292582
Basically it sounds like the computer has invalid data in the registry for one of the built in directories that Windows Installer resolves. It's an environmental issue rather then installer logic issue.
I'd have to see the installer log and computer registry to confirm or deny that though.
I had the same problem recently (with Installshield 2015). The problem was, that under Application Data/Files and Folders there was a definition for a folder called .. - so the setup would try to create a folder .. on the target system, which of course doesn't work.
Deleting that folder definition and moving its contained files to the parent folder definition fixed the problem for me.