My co-worker is able to deploy our projects to AWS Elastic beanstalk fine. However I have issues on both my work machine and my home laptop. Both computers have the same error in AWS window pane.
I get a pop up as follows:
Deployment of the website failed due to errors during build of the deployment archive,
check visual studio output window 'Build' and/ or 'Amazon Web Service' panes for more details.
Then in the amazon window pane I get a different error everytime I try to run the deployment.
Example 1:
...package build 'CopyPipelineFiles': error in 'C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\Web\Microsoft.Web.Publishing.targets' at (1413,5): Copying file Web.config to obj\AmazonDev\TransformWebConfig\original\Web.config failed. Could not find file 'Web.config'.
Example 2:
...package build 'TransformXml': error in 'C:\Users\Andrew\colony\colony-website\Colony.Web\Colony.Web.csproj' at (840,5): Could not open Transform file: Could not find file 'C:\Users\Andrew\colony\colony-website\Colony.Model\Web.AmazonDev.config'.
Seems to be a different error each time -- I'm not sure how to even begin to look for any issues.
Jim Flangagan's comment is the answer: ReSharper 8.2 is causing this problem. To resolve either disable resharper ( Tools>Options>ReSharper>General>Suspend Now) or upgrade Resharper.
Related
I decided to publish the ASP.NET MVC project to test it locally using IIS Manager. Therefore, after opening the necessary windows features, I created a new folder in the C:\inetpub\ directory on IIS Manager:
In the Visual Studio IDE I right clicked on the solution and clicked "Publish..." and specified that the target was "Folder":
When I clicked the Next button, I specified in the next window that the "Target" location was the C.\inetpub\TechnologyArticle directory. Then when I clicked the "Publish..." in the Visual Studio IDE, I encountered an error that I did not receive in Debug mode:
System.AggregateException: One or more errors occurred.
---> Microsoft.WebTools.Shared.Exceptions.WebToolsException: Build failed.
---> (Inner Exception #0) Microsoft.WebTools.Shared.Exceptions.WebToolsException: Build failed.
---> Microsoft.WebTools.Shared.Exceptions.WebToolsException: Build failed.
How can I solve this problem? Is the reason why I got this error in Release mode, which I did not receive in Debug mode, due to programming?
This error is not due to programming. The reason for this error is trying to publish the website in the C:\inetpub\ directory, which is made visible and/or created by a service that you have activated by "Turn Windows features on or off" to publish the ASP.NET website locally. The user has no right to modify the C:\inetpub\ directory. Therefore, the current user's right to modify the C:\inetpub\ directory must be declared manually in the Windows 10 operating system.
When the ASP.NET website is published, the project outputs (such as *.dll files, style files, scripts, Views) compiled in Release mode will be extracted to the target directory, so the user must have the right to write to the C:\inetpub directory.
To resolve this issue, follow the steps below:
Open the properties of the C:\inetpub folder (With the folder selected, use the ALT + ENTER shortcut).
Switch to the Security tab and click the Edit button.
Define "Full Control" right for current user and confirm settings by clicking OK button.
You repeat the publish procedure to publish your website.
I've made my web app on Blazor server-side and I'm trying to publish it on a windows server.
I tried different methods to publish but all came to the same conclusion.
HTTP Error 500.30 - ANCM In-Process Start Failure
Here comes a link to the image:
https://drive.google.com/file/d/1ndgb9Bh5BJH-tp_vR5vpfhWcr8BFgyh2/view?usp=sharing
As you can see there is no index file! why that's missing?
I used this instruction:
https://www.c-sharpcorner.com/article/deploying-a-blazor-application-on-iis/
Why am I having this problem?
You can see the result on mangoscarf.com
"ANCM In-Process Start Failure" is a generic error.
To get more information about the error go to:
Azure Portal > your App Service > under development tools > open Console.
You can run the application through this console and you should see the actual error.
(Type the executable filename of your project, i.e. "omgwtf.exe" and press enter.)
Also check here: https://learn.microsoft.com/en-us/aspnet/core/test/troubleshoot-azure-iis?view=aspnetcore-5.0&viewFallbackFrom=aspnetcore-5
I used this method:
Select the folder from the left menu and provide a folder path. You can provide any folder path where you want to publish your app.
Click on publish. Visual Studio will start publishing your application. If there are no build errors, then your application will be published successfully in the folder you have mentioned.
After the publishing is successful, you should move on to configure IIS.
more info on:
https://www.c-sharpcorner.com/article/deploying-a-blazor-application-on-iis/
I'm building an ASP.NET MVC application and when every time I start debugging, it throws an error
Process with an ID (Random number every time) not running
in Visual Studio 2015 Enterprise.
Also in the output window, I see the following lines:
The program '[10144] iisexpress.exe: Program Trace' has exited with code 0 (0x0).
The program '[10144] iisexpress.exe' has exited with code 0 (0x0).
What I tried:
deleting .VS folder in the solution
deleting IISExpress folder in My Documents
changing project URL of the web site
checking out 'Use 64bit version of IIS Express' in Tools > Options > Projects and solutions > Web projects
deleting DEvelopmentServerPort, DevelopmentServerVPath and IISUrl in CSPROJ.
repairing IISExpress from Add/Remove programs.
like most of every solution I could find in StackOverflow and every where in the web.
According to your description, I suggest you could try below solution.
1.Open your project file (csporj): Upload the project and right client the project file.
2.Find DevelopmentServerPort, if it contains and delete it then reload the project.
If this solution doesn't solve your issue, I suggest you could try this solution.
Eidt
If your machine is 64bit, please go to Tools-> options -> projects and solutions:
Could you please tell me this issue is only occured for current MVC application? If you start a new web application, it will work well.
If above solution doesn't solve your issue, I suggest you could try to use process monitor to find how IIS work.
Details about how to use process monitor, you could refer to below steps:
Download Procmon tool from https://learn.microsoft.com/en-us/sysinternals/downloads/procmon
Open Procmon.exe as Administrator.
3.Remove all the filters -> then Apply -> then OK
4.Make sure the telescope icon is shown as below, this indicates the capture is ongoing
5.Then reproduce the issue
Press CTRL + E to stop the trace capture
Press CTRL + S to save the log
Click "All events", Save log as "Native Process Monitor Format (PML)".
9.If this pml doesn't contain the importent data,you could share the pml to me to analysis it.
I have code coverage enabled on TFS 2013. I work with MSBuild.SonarQube.Runner 1.0.1. When I run the End phase of the Analysis. I get the following error messages:
11:36:00.269 Failed to convert the downloaded code coverage tool to XML. No code coverage information will be uploaded to SonarQube.<br/>
Check that the downloaded code coverage file (C:\Builds\39\[product name]\System_Main_Release_Code_Analysis\.sonarqube\out\VSCodeCoverageReport.coverage) is valid by opening it in Visual Studio. If it is not, check that the internet security settings on the build machine allow files to be downloaded from the Team Foundation Server machine.
Post-processing failed. Exit code: 1
An error occurred while copying diagnostic activity logs to the drop location. Details: Forbidden
On the build server there is no VSCodeCoverageReport.coverage file - at least not at the indicated location and with that name. However, when I click on (Coverage Results) in the TFS Build summary, a coverage file is downloaded that opens up in Visual Studio in the Code Coverage Results Window.
What could be the issue?
The problem is solved.
The proxy settings on the build agent had changed. This resulted in http requests to the TFS server or any local addresses to fail.
It was particularly challanging to figure out, because the Agent build log that tells you all the details of a build is the file that could not be transferred to the drop location. So I used ProcMon from Sysinternals with File monitor enabled during a build. A comparison between a successful build in the past and a current failed build showed me which file was missing (the agent log file). A search in ProcMon for this file revealed where that file was located on the build agent. The Agent Log file contained the Downloading coverage file from {0} to {1} line Dinesh was looking for in his attempt to help me. That http address pasted into a browser showed an "Access denied" message.
From there it was a logical step to analyse the Proxy settings. What finally solved it was to check "Bypass proxy server for local addresses" in the Local Area Network (LAN) Settings"
I've found a few posts mentioning this error, but none that have helped. I created a new C# Windows Store project, and when I try to build and run it on the simulator, I get the following error in visual studio:
Error 1 Error : DEP0700 : Registration of the app failed. error 0x80072EE4: The Visual Elements extension failed while processing the Notification element. (0x80073cf6) TestDeploy
Here are the details from running a Power Shell command mentioned in a different post:
12/18/2012 3:03:59 PM 404 Error error 0x80073CF6: AppX Deployment operation failed. The specific error text for this failure is: error 0x80072EE4: The Visual Elements extension failed while processing the Notification element.
12/18/2012 3:03:59 PM 401 Error Deployment Register operation on Package cc8bb3bb-d444-4dbe-ae12-64684b12b727_1.0.0.0_neutral__2awvr17ztw74c from: (C:\Users\myself\documents\visual studio 2012\Projects\TestDeploy\TestDeploy\bin\Debug\AppX\AppxManifest.xml) failed with error 0x80073CF6. See http://go.microsoft.com/fwlink/?LinkId=235160 for help diagnosing app deployment issues.
12/18/2012 3:03:59 PM 605 Information The last successful state reached was PackagesInUseClosed.
12/18/2012 3:03:59 PM 300 Error error 0x80073CF6: Cannot register the cc8bb3bb-d444-4dbe-ae12-64684b12b727_1.0.0.0_neutral__2awvr17ztw74c package due to the following error: Package could not be registered.
.
12/18/2012 3:03:59 PM 316 Error error 0x80072EE4: Cannot register the cc8bb3bb-d444-4dbe-ae12-64684b12b727_1.0.0.0_neutral__2awvr17ztw74c package because the following error was encountered during the registration of the windows.visualElements extension: <Error message string not found>.
12/18/2012 3:03:59 PM 306 Error error 0x80072EE4: While installing the cc8bb3bb-d444-4dbe-ae12-64684b12b727_1.0.0.0_neutral__2awvr17ztw74c package, the system failed to register the windows.visualElements extension due to the following error: <Error message string not found>.
12/18/2012 3:03:59 PM 5092 Error error 0x80072EE4: The Visual Elements extension failed while processing the Notification element.
12/18/2012 3:03:57 PM 10002 Information Creating Resiliency File C:\ProgramData\Microsoft\Windows\AppRepository\4850558d-7f7f-4109-9376-3b78bf5acc86_S-1-5-21-1715567821-179605362-839522115-27106_1.rslc for Register Operation on Package cc8bb3bb-d444-4dbe-ae12-64684b12b727_1.0.0.0_neutral__2awvr17ztw74c.
12/18/2012 3:03:57 PM 603 Information Started deployment Register operation on a package with main parameter: file:///C:/Users/myself/documents/visual%20studio%202012/Projects/TestDeploy/TestDeploy/bin/Debug/AppX/AppxManifest.xml. See http://go.microsoft.com/fwlink/?LinkId=235160 for help diagnosing app deployment issues.
12/18/2012 3:03:57 PM 301 Information The calling process is C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\devenv.exe
Any ideas? I've given full control to everyone on the project, have restarted multiple times, tried reinstalling visual studio, and am running Visual Studio as an administrator. Any help would be appreciated!
I got this to "work" by killing and restarting explorer.exe based on suggestions from a different google search I found. Doesn't really make sense to me, or seem to work reliably, but it does work sometimes at least... o.O
edit
A more permanent solution that worked was some combination of reinstalling Visual Studio 2012 and installing Visual Studio Update 1.
I was getting the same error and in my case neither cycling explorer.exe nor uninstalling/reinstalling Studio 2012 Ultimate with Update 3 worked.
What did work was starting up Visual Studio 2012 with "run as Administrator"
Seems, the issue has to do something to installing app both to local machine and to simulator
My case is i duplicate a WP 8.1 project and add merge some code to the duplicated project.
After i done the merge, I got "Package can't be registered" message when i deploy it to emulator.
But my original WP 8.1 project is successfully running on the emulator.
The root cause is i delete some app logo png image.
The VS2013 wont tell u that image is missing but display "Package can't be registered".
Hope this helps.
This happened to me after uninstalling a custom app that was installed using VS and trying to re-install a new version through either VS or directly using the Add-AppDevPackage.ps1 script
While it is not what you want to hear, a reboot fixed this for me. I tried killing the explorer process and restarting it as mentioned above, but this did not work for me.