The Overflow Blog. Podcast Making Agile work for data science. Stack Gives Back Featured on Meta. New post summary designs on greatest hits now, everywhere else eventually. Linked 0. Related 2. Hot Network Questions. Question feed. Stack Overflow works best with JavaScript enabled. INFO: Begin assembly probing. INFO: End assembly probing. We've just had this exact same error but the cause was so misleading compared to the error it's hopefully worth adding here as it comes top on google The "The application has failed to start because its side-by-side configuration is incorrect" error was occurring when starting a windows service.
In our instance this was caused by the services application. Amending this resolved the "not related in any way whatsoever" error message. The quickest way to check this would be to paste the xml file into one of the many on-line xml validators free on the web. Yes, that can only be found on a machine that has Visual Studio installed. The DebugCRT is not distributable.
Deploy the Release build version of your DLL. This is marked C , so I'll give the C answer: Something has mangled your projectname. Pull it up in a text editor and chances are something won't be closed properly or there will be a few garbage characters at the end. You can figure out why that happened later. But for now, just fix it and you'll be able to launch. You can just delete the manifest file from your application path, then the executable will work properly,.
I found side by side error there is a mismatched or system error in app. The file needs to be in UTF-8 , while you can actually get ANSI accidentally nowadays by creating configuration file manually using notepad. I had this issue and it was a simple problem with the version value in assemblyIdentity element of the app. Apparently version must have all four numbers unless assemblyIdentity is ignored which is the case if the manifest is embedded. In my case, I was working with a console application which is build in c and I was using VS I tried to publish the code by right clicking on the project and select the publish option and then configure the required settings.
I was googling that error message and I came across this question. This answer may seems irrelevant to the question but still I am posting my answer for the folks like me who got here because of facing problem like mine. So I found the salutation for my problem as below steps :. If something from your App.
For example, in the app. The issue was related to a dependency mentioned in the manifest file:. Depends is not great with side-by-side dependencies because it can often make it look like the dll is found when actually a slightly different version was required.
The event log usually shows side-by-side errors but sadly these don't give you much information other than that you have a problem.
Before installing, make sure that the "bit compilers and tools" feature was selected when installing the Visual Studio proper. If you install it after installing SP1, you will probably need to uninstall and reinstall the SP to get the fix. The reason is a bug in VS installer.
While the feature containing the x64 DebugCRT shared assembly component is "advertized" rather than installed for some reason.
Whatever is the cause, VS SP1 fixes it. Its installation has a side effect: it also forcibly installs many other features that may or may not have been selected during VS install e. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Asked 9 years, 11 months ago. Active 3 years, 4 months ago.
Viewed 13k times. I am working on a bit OS windows 7 ultimate machine VS with 64bit addon. The 64 bit debug is not launching; it gives the error: Unable to Start program xxx This application has failed to start because application configuration is incorrect. This probably means you are trying to run a debug build on a machine that does not have Visual Studio installed. The solution to the problem is to build and distribute a release build, not a debug build. Thanks Scott. What I am wanting to do is the remote debugging.
I would like to run code at Visual studio on one machine, and the debugging version a. Do I have to install Visual studio on the 2nd computer?
0コメント