I have a vsix package that has been built and installed on my machine and works well. I tried a double click install on a machine that does not have the VS Sdk. When I click on the icon in the View-OtherWindow I get an error that says "exception has been thrown by the target of the invocation". Any thoughts?
The VS SDK is not required on the target machine to deploy a VSIX. It is possible that you are relying on DLL's from the SDK which need to be deployed with the VSIX. That's just idle speculation though because the exception message is very vague.
The best way to tackle this problem is to hook up a debugger on the target machine and see what the root cause exception is. Knowing that will help us track down this issue.
Related
I simply wish to install Visual Studio 2017 to compile a project.
Trying to install via the installer obtained from Microsoft fails after being unable to obtain the .opc file from aka.ms (found that after checking logs in %Temp%)
Moved to a full install version with all files and .opc file present. Installer still attempts to download from the web. Fails saying it is unable to download.
Tried running installed with --layout pointing toward the location of the offline files, same error.
Installed certificates from the certificates folder both in Personal and Trusted Root stores, no difference.
Tried starting CNG Key Isolation service, fails with error 1053
Microsoft support transferred me three times before saying the problem is on their end, so how, if one were to have no internet connection and evidently has all files required for install available, install this, if the installer stubbornly attempts to download from the web?
Is there a KB I am missing or some procedure I have to follow with the full installers?
In my case it is the network firewall blocking the downloading because the downloading involve not only main Microsoft visual studio site which is allowed in our network but also some url like https://aka.ms which is blocked by our firewall.the error is listed in c:\users\myusername\appdata\local\temp\dd_bootstrapper_xxx.log
It appears from what you have submitted you are attempting to download a offline copy of Visual Studio. It also appears that you are attempting to run the file originally downloaded to create the bootstrapper for the installation.
You want to instead launch the setup executable which is actually in the layout folder.
Hope this helps. ^^
Appears the cause for this was the service disclosure debug, disabling the debug, binding all services back into the svchost and after rebooting the service is working again. I have been able to install VS now.
I have been battling DEP3321: To deploy this application, your deployment target should be running Windows Universal Runtime version 10.0.14393.0 or higher. You currently are running version 10.0.10586.839. Please update your OS, or change your deployment target to a device with the appropriate version. for the past few days.
I have a UWP app which I cannot run on my machine. However, if I select one of the emulators, it runs fine. I have also set the minimum target value which ensures that the app runs, however, the app throws an error as it cannot find some methods in the lower version on the SDK.
I have tried repairing and uninstalling/re-installing both visual studio 2015 and 2017. I have tried the same with the various windows SDK as well. At one point i had three different versions of the SDK installed and visual studio was still complaining even though i had the updated version installed. Currently, I have installed win sdk 10.0.15063.17.
Any ideas what I can do next to resolve this issue. I have trawled various SO pages as well social.msdn pages with no luck.
Many thanks
I just started a new app and selected the highest Target levels and got this error. I was able to get rid of this error by selecting the default minimum Min Target Version as shown below.
I also encountered the same problem
Severity Code Description Project File Line Suppression State
Error DEP3321: To deploy this application, your deployment target should be running Windows Universal Runtime version 10.0.17763.0 or higher. You currently are running version 10.0.17134.648. Please update your OS, or change your deployment target to a device with the appropriate version.
Solution:
Right click on the project property and got to the General-> Target Platform Minimum version.
In my case, I changed it to "10.0.17134.0" by selecting from the drop-down and then rebuilt it.
I worked well. Attached snapshot for reference.
If your app is using APIs that only exist in newer versions of the OS (like 14393 or 15063), then you won't be able to call those on 10586. You will get an exception because the method simply doesn't exist on that machine.
In order to support the app on lower versions of the operating system you will need to wrap the calls to those APIs with an appropriate "IsAPIPresent" check:
https://learn.microsoft.com/en-us/uwp/api/Windows.Foundation.Metadata.ApiInformation
Thanks,
Stefan Wick - Windows Developer Platform
Possible Solution:
I was facing with the EXACT same issue. I have my SDK 15063, and I have installed Visual Studio 2017 afresh, which also installed SDK 15063 implicitly, but I still kept on getting the same deployment error DEP3321.
I solved this issue in this way -
Just go to the "Solution Explorer", on the right side of Visual Studio and do the following steps in this order -
1) Just right click on the project you are deploying
2) Press "Unload Project"
3) Right click on the project_name(unavailable) and press Edit project_name.jsproj. It will open an xml file on left hand side
4) Search for "TargetPlatformVersion" and "TargetPlatformMinVersion". Both are placed next to each other. Mine looked like this -
10.0.15063.0
10.0.15063.0
since mine Error DEP3321 explicitly stated that 'you are currently running version 10.0.14393.1715, so I replaced my "TargetPlatformMinVersion" from 10.0.15063.0 to 10.0.14393.1715 -
10.0.14393.1715
5) Now save it, Ctrl+S
6) Right click on "Solution Explorer" and press Reload Project and press Yes to the popup if you get stating that project is already loaded.
You are done. Just do what you normally do, Build (ctrl+shift+B) and then Debug - F5 or Ctrl+F5.
This way the project got deployed for me.
All the sudden started getting the following error while trying to debug a worker role:
"Windows Azure Tools for Microsoft Visual Studio
There was an error attaching the debugger to the role instance 'deployment16(360)blah blah' with Process Id: '8780'. Unable to attach. The Microsoft Visual Studio Remote Debugging Monitor has been closed on the remote machine."
Restarting Visual Studio and the machine do not help.
As you start getting this problem all of sudden in your development machine something must have changed and it is mostly due to some of the OS auto-update and/or some application update you installed in your machine. There could be any random reason for this problem however if I would have hit the exact same problem here is what I would do to troubleshoot such issue:
To start, first thing is to just check it is not an application specific problem by creating a base app from web/worker template and see if that exhibit the problem.
If you have installed new release Windows Azure SDK 1.7 check with both SDK 1.6 and 1.7 to verify if both exhibit the problem.
Check if your could debug IIS based application as well outside Compute Emulator. This will isolate if the problem is specific to Windows Azure development Fabric or bind to your IIS itself.
If this is IIS specific issue, Check IIS configuration for all enabled functionalities, try resetting Application Pool configuration, running "ASPnet_regiis -i" etc to fix the issue.
If it is Windows Azure Computer Emulator specific, I know sometime OS updates may make application unstable so in that case, I will re-install .net 4.0 and VS2010 SP1 again respectively. (This does help so many time) then re-install Azure SDK 1.7 completely.
Such random problem mostly occur due to some change in your machine configuration, so restoring the VS2010 and the re-installing all other application does help to solve problems.
If you have an exception in the role's OnStart() or in Application_Start() that the debugger doesn't pick up, you may also receive this message. Application_Start() errors are especially pernicious because the debugger doesn't attach to the web process until after this method returns.
If you are wedded to cloud specific classes such as RoleEnvironment and cannot make the web role a startup project, you can use Ctrl-F5 to run the cloud project without debugging. With some luck you'll get a yellow screen of death to show you the true error.
Avkash covers the points.
I had the same issue recently. I set my web project as start-up rather than Azure and I discovered that that web project didn't actually run. Turned out somehow when of my projects was compiling for X64. I changed that and it worked.
I recently installed Visual Studio 2010 to help me with some exercises for class.
It all worked great in school but when I got home and tried to run and debug the second program I got this error:
Unable to start ...\Kapitel_1\Debug\Kapitel_1.exe
This application has failed to start because the application configuration is incorrect. Review the manifest file for possible errors. Reinstalling the application may fix this problem. For more details, please see the application event log.
How can this be solved?
This message generally means that the machine on which you built the application did not have the same redistributables than the system where you run the application.
Redistributables are sets of DLLs needed for your application to run properly.
In your case, I noticed that you are trying to run a debug build. That might just be the problem: you cannot run an application or use a DLL that has been built in debug configuration on a system with no debugger installed. Installing Visual Studio (ideally the same version your school has) should do the trick. You could also rebuild your application in Release configuration to avoid having to install a debugger on the running system.
Another case where this error message might be displayed is if you just installed a new Visual Studio update on the system that built the application and not on the system where you are trying to run it. In that case, you would need to update your system with the latest set of redistributables from Microsoft (at time of writing, here was a good place to look for that).
This question already has answers here:
The application failed to initialize properly (0xc0150002)
(5 answers)
Closed 5 years ago.
my mfc application created in visual studio 5 running on windows server 2000 sp4, i create a release for it and try running it win xp slp2. it gives me application failed to initialize properly (0xc0150002)
i have tried following things
-Install Microsoft Visual C++ 2005 SP1 Redistributable Package (x86) the one that comes within the release folder as well as one downloadable from website
copied all dll and mainfest from microsoft visual sutdio\vc\redist
I still keep receiving the same messsage. c
what could be wrong?how can i fix it
some things to check:
check the /SUBSYSTEM linker option for you project. It might include OS major/minor version numbers.
ensure that you are using appropriate Windows XP PlatformSDK on DEV machine; check values of WINVER, _WIN32_WINNT
use depends to see whether the problem is in unresolved dependencies
check the version of runtime that your application requires with that on target machine. I usually do this by looking at the app's manifest from one side and into WinSxS folder of the target machine from another (recently there had been an ATL Security update from Microsoft http://msdn.microsoft.com/en-us/visualc/ee309358.aspx; new binaries created by updated Visual Studio will not run on machines that haven't the same updated version of runtime).
It is possible you have applied a security update or compiler update to your VS2005 SP1. That makes it generate a manifest that requests a different MFC/CRT-dll than the one installed with Microsoft Visual C++ 2005 SP1 Redistributable Package (x86) .
Try to use Depends.exe and open your application, then in the menu choose "Profile". Look in the output window below for a more detailed description.
Are you trying to run the debug version? That may give you an error similar to 0xc0150002. Try the release build, or you could compile against the static libraries rather than dynamic libraries. If you get this problem on a release build then the chances are that it's a missing dll (in which case try running Depends.exe) or an incorrect manifest.
If you have a missing dependency on a runtime dll you could try creating a deployment project for it as this will detect the appropriate runtime dlls and build it into an installer for you.