The app works fine after it starts but it consistently takes about 60 seconds + high CPU before my code starts executing. When I run the app from Visual Studio or via the old click once install it starts instantly.
The .msix file is about 130 MB. The app has a dependency on the Crystal Reports runtime. I used the MSIX Packaging Tool to create the package for the Crystal runtime, then I added my app to that package.
I'm stumped.
Related
I am on VS 2019 16.8.3 with .Net 5.0.
I have created a simple Win Form project without any NuGet or project dependency. I have made sure it runs out of the IDE.
When I published the project to a self-contained single file exe, it does not run. The Task explorer briefly showed the exe and switch it to suspended before killing it. The exe works fine after I republished it either without the single-file or the self-contained option. It seems like both options cannot co-exist.
Any idea?
When I just installed a Visual Studio 2017 and created my Xamarin.Forms application, it ran fine on my Windows 10 PC. However, I then installed some apps from Steam (which is the only thing I can think of that could change system settings). After that, when I try to create another Xamarin.Forms project, it does not deploy well to my machine and gives the following error:
DEP6200: Bootstrapping failed. Device cannot be found.
SmartDeviceException - Deployment failed because no
device was detected. Make sure a device is connected
and powered on. [0x80131500]
Strangely enough, my first app continues to build and run fine, even if I uninstall it from Windows and then deploy it again.
What could be the issue?
I have just noticed that Visual Studio makes ARM the default architecture. Changing it to "Any CPU" brought back the option to run the app on my machine.
I am having an issue with Visual Studio 2017 RC where when I run an MVC and/or WebAPI app using IIS Express the app never actually runs. Instead I get stuck with a page in the browser indicating it is trying to attach and from there it goes no further. If I open another tab/window in the browser and try to navigate directly to the launch URL, it just spins forever. Likewise when I run this using the dot net run command, the app launches and runs fine.
There do not seem to be any errors that I can see, just that the browser spins indefinitely without actually ever loading the page/endpoint.
Note: this occurs for most any circumstance. Newly created project in VS with no changes, known working project from previous versions, etc.
You could follow or upvote the issue: https://developercommunity.visualstudio.com/content/problem/11391/aspnet-core-iis-express-httplocalhost51733-failed.html
Looks like our workarounds meanwhile are
dotnet run
Publish to local IIS. Which is working for me.
(Untested: downgrade from core-1.1 to core-1.0)
If you aren't familiar with VS2017/asp.net:
You have, or can reveal via View Menu-->Other Toolbars :
Debug toolbar --> dropdowncombobutton saying "[green arrow>] IIS Express"
Click on the dropdown downarrow part of the button.
You should see a Run {yourprojectname} option.
This is the equivalent of dotnet run {yourprojectname} from the commandline.
You can configure the options that appear in the dropdown with
Right-click on project in solution explorer --> Properties --> Debug
I had this same issue and after digging around for a while I discovered that I had dotnet preview v1.0.0-preview2 installed under Programs Files (x86) and a non-preview version in x64. I think VS is launching the x86 (preview) version but expecting to see the full version. To fix this, I did the following.
from programs and feature uninstall every visible dotnet core. (note: for me this did not remove the x86 preview)
go to https://www.microsoft.com/net/download/core#/sdk and install BOTH x86 and x64 SDK packages
open command line and from the root directory check run: dotnet --version (at the time of writing it was 1.0.4)
fire up .net core project in VS 2017 and run.
When I did all of the above, I was able to start up the site in IIS Express from VS.
Every site my asp.net site starts, Visual Studio C# Command line compiler starts running. It takes more CPU space and continue to run for few hours.
While it is running my sites does not open.
I facing this problem very badly and need some help.
My Server with Xenon CPU, 8 GB Ram and windows 2012 installed on it.
Thanks
Are you doing compile at run-time? Consider pre-compiling the application to solve this problem.
Refer: https://msdn.microsoft.com/en-us/library/aa983464(v=vs.110).aspx
I am using visual studio 2010 in windows 7, i am running Normal distribution code which uses pcl header files. The entire code is in cpp. While debugging i am get an application error
" The application was unable to start correctly (0xc000000d). click ok to close the application " in an new window. while i click ok, the window gets closed and programs stops running. In the output tabs, shows unable to load or cannot find pdb files.
Following steps i created the Visual studio project
downloaded the pcl trunk version which only consist the header files for Normal distribution
using cmake, i created the install visual studio project for installing pcl
After creating INSTALL project, installed the pcl headers using visual studio
again using cmake, i created the Normal distribution project which make use of installed pcl headers
while running the Normal distribution project, i am getting the above mentioned application error. I am unable to find what is the problem