Premise: I'm a frontend web developer and I had to launch a project written in C# that has many dependencies. I tried to set the enviroment but I had many issues, this is one that neither I, nor the people around me, can resolve (at least we couldn't until now).
When I try to run the solution it always throws an error and open a popup where it writes something like "it is not possible run Azure storage emulator. Run AzureStorageEmulator.exe as administrator and try again". I tried to run the command but it tells me that it is not installed. I unistalled and installed again the Azure SDK, still the error, I installed the storage emulator from here https://learn.microsoft.com/en-us/azure/storage/common/storage-use-emulator#using-sdk but nothing.
What can I do?
I'm using Visual Studio 2019, .net core 2.2 and Azure SDK
Sorry for my funny English, I'm not native.
Related
I have a blank UWP C# application that I would like to connect to an Azure SQL database using MFA.
Targeting version: Win10 version 1903 build 18362
Min version: Win10 Fall Creators Update build 16299
I've attempted to use references like System.Data.SqlClient/Microsoft.IdentityMode.Clients.
But my application does not like the reference. When clicking into it, it tells me the project cannot be viewed in the object browser. I tried reinstalling it different ways with no luck. Also downloaded all the recent Windows 10 SDK versions.
reference error
Whats the best approach to this and if anyone has resources that could help me out.
I have been trying to get a successful build for my game in Unity 2018.2.1f1 and Visual Studio 2017 15.8.0.
After trying unsuccessfully to get a successful build / package / WACK for the windows store with all/every different configuration, I tried a totally blank default Unity, UWP platform app, generated a visual studio project. generated some icons, associated it with an app I had in the store. Built it, packaged it and run the WACK tests.
FAILED
Supported APIs
Error Found: The supported APIs test detected the following errors:
API ExecuteAssembly in uwphost.dll is not supported for this application type. WinTest2.exe calls this API.
API DllGetActivationFactory in uwphost.dll is not supported for this application type. WinTest2.exe has an export that forwards to this API.
Impact if not fixed: Using an API that is not part of the Windows SDK for Microsoft Store apps violates the Microsoft Store certification requirements.
How to fix: Review the error messages to identify the API that is not part of the Windows SDK for Microsoft Store apps. Please note, apps that are built in a debug configuration or without .NET Native enabled (where applicable) can fail this test as these environments may pull in unsupported APIs. Retest your app in a release configuration, and with .NET Native enabled if applicable. See the link below for more information:
What do I have to do to make a successful app build that I can actually get into the store. (What configuration, what unity / visual studio versions.) I have tried later versions of unity 2018.2.1 and 2018.2.2 (i think) and could not get a successful build out of them.
A while ago, i could not get a successful build out of Unity, so I reinstalled Win 10 Pro, Unity and Visual Studio. Still problems persist.
Thanks to StormBringerStudios I received an answer that works.
"Just Got Visual Studio 2017 15.7.6 version. works like a charm.
So here is my Solution is anyone will search this kind of problem DONT USE VS 2017 15.8.X.
Downgrade to 15.7.6 and you will be good :)
Microsoft certification also passed."
I've been trying to setup mobile development on VS2015 for several days. The issue is
I created blank app
Started Emulator From Xamarin Android Player
Started Debugging
I got my solution built succeed but deploy failed. Here is image
I checked the error list but as we can see it is nothing there.
Well, I searched on internet with different queries and came to know that this problem is quite common but no permanent solution is provided. Some of the solutions suggested on other sites including Xamarin Official Forums are as follows:
Restart debugger.
Install valid Java Sdk Manager.
Restart Visual Studio.
Install android packages for targeted platform.
Create virtual device.
Change settings in Hyper-V manager.
Set your project as Startup Project.
Uninstall android components and reinstall them.
Disable Fast Deployment Option in Project Properties.
I tried everything but issue stands still. The packages I have installed for SDK are in image as follows
I don't know what part of package installation I am missing or there is some problem with VS2015. I have been trying to resolve this deployment issue but in vain.
Note*: I am using HP EliteBook 8460p with Win 10 64-bit installed on it.
I am an experienced ASP.NET developer and familiar with Visual Studio and IIS. But I'd like to deploy ASP.NET applications to Mac OS X using Mono. I've done a LOT of searching on the web and can't a simple straight forward way to deploy a site on a Mac. Everything I've found does NOT give the whole picture.
I've downloaded the current Mono release (3.2.4) from http://www.go-mono.com/mono-downloads/download.html. But I don't think the installation package is complete. For example, I can't find any mod_mono compiled binaries. The mod_mono.conf file is supposed to reference mod_mono.so, but I can NOT find installed anywhere from the installation package. I found the mod_mono source at on a link from the above page, but don't know how to compile and deploy.
Also creating the mod_mono.conf is another issue. There is a configuration tool at http://go-mono.com/config-mod-mono/Default.aspx, but it doesn't work in my setup.
The only success I've had, is with the xsp server tool. I think it is meant for testing and NOT deployment.
BTW, I am running OS X Mavericks 10.9.1. I only want to deploy to Mono. The development is done under Windows with Visual Studio.
Could someone guide me? I am obviously missing some steps.
I am using Visual Studio 2012 using C#.
I am getting error while opening the project at my PC, this project is working fine on another system.
Very frequently I am also getting this error too.
how many instances are you trying to run? small hint here, try to run the emulator before you run the solution, it helps sometimes. Second try it with the express emulator feature (new since sdk 2.1)