Develop Reference

Problem with AzureStorageEmulator.exe Azure SDK and Visual Studio related

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.

Totally Blank Unity / Microsoft Store Build fails WACK tests

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."

Can't add Azure CloudService Project to existing solution

Goal: Convert an existing MVC application running on Azure AppServices to run on Azure CloudService. (need to add a library that needs this)
Problem: Error message (below) and the CloudService role appears non-functional
Visual Studio 2017 (15.2 (26430.6))
Actions:
Added new Cloud Services project to the existing solution
Did not add any roles
OK (project created without error)
Added a Role to the CloudService project
"WebRole in project"
Selected the MVC application that already existed in the project
Press OK, error occurs
Note, the project described in the error is the MVC project (not the CloudServices one), so we also removed the NuGet reference and retried with the same result.
Error (retyped):
Microsoft Azure Tools for Microsoft Visual Studio
The following NuGet packages could not be installed in project XXXXXXXXX:
WindowsAzure.Storage (version ‘(unknown)’): Value cannot be null. Parameter name: path1
Ideas?

I found the problem here...stinky error message
The problem was that the Azure SDK was not installed correctly. Modified the installation to include the Azure workload and this fixed the problem.
The Convert to Azure Cloud Services became available and that seems to have worked.
There was no message that the workload was not installed, perhaps because the machine had a version of the Azure SDK installed from previous work in VS 2015. Dunno.

VS2015 Community ASP.NET5 Dependency injection and azure publish errors after UWP update

Until recently i had working asp.net 5 mvc webapi project. It worked locally and i was able to push it to azure cloud (publish option).
About week ago i started to work on universal windows app for rasberry pi 3 - so i installed necessary package (Visual Studio Tools for Universal Windows Apps) with couple more updates from gallery (new version for ASP.NET and Web Tools probably).
When i got back to working on webapi project i've noticed warnings:
DOTNET1015 The 'compilationOptions' option is deprecated. Use
'buildOptions' instead.
DOTNET1015 The 'exclude' option is deprecated. Use 'exclude' within
'compile' or 'embed' instead.
DOTNET1015 The 'publishExclude' option is deprecated. Use
'publishOptions' instead.
in my project.json file
So something must have changed after those updates.
Project build passes but when i start it locally on debug and IIS Express i get:
An unhandled exception of type 'System.InvalidOperationException'
occurred in Microsoft.Extensions.DependencyInjection.Abstractions.dll
Additional information: No service for type
'Microsoft.Extensions.PlatformAbstractions.IApplicationEnvironment'
has been registered.
And when i try tu push it to azure i get some errors in my language (polish) about metabase problems and wrong format of paths eg. lm/w3svc//ROOT/
my project.json file: http://pastebin.pl/view/f823f093
VS info: http://pastebin.pl/view/86bae236
I try to clean and rebuild solution, restore packages but its probably something else.
What can i do except of uninstalling VS and instaling one more time?

Complete uninstall of VS 2015 Comunity and clean install of AspNet5.ENU.RC1_Update1_KB3137909 did the trick for me. Problematic update probably was
https://visualstudiogallery.msdn.microsoft.com/c94a02e9-f2e9-4bad-a952-a63a967e3935?SRC=VSIDE

Azure Cloud Service: "Requested registry access is not allowed". VS2015

I've been trying for days to migrate our backend solution running on Azure 2.6 and Azure Cloud Services to Azure 2.7 in VS2015 on Windows 10 workstation, but without any luck.
I've tried on multiple computers using a clean install of Windows 10 Pro x64 with Visual Studio 2015 Enterprise (all features installed).
All updates available in both Windows Update and Vs2015 are installed.
I create a new Cloud Service solution, with one Empty web role.
I've set VS2015 to break on "Common Language Runtime Exceptions" (Debug -> Windows -> Exception Settings).
I've run into the same errors on a separate machine running Win 8.1, VS2015, Azure 2.7.
The solution compiles fine but when I try to run/debug the Cloud Service project it throws the following error:
Exception thrown: 'System.Security.SecurityException' in mscorlib.dll
Additional information: Requested registry access is not allowed.
Starting only the WebRole without using the CloudService works.
When I try to run the CloudService through VS2015 with administrator priviliges the following exception is thrown:
'System.Threading.WaitHandleCannotBeOpenedException' in mscorlib.dll
Additional information: No handle of the given name exists.
Publishing the compiled solution to Azure yeilds the same exception when inspecting the intellisense logs ("Requested registry access is not allowed").
I've tried to add the install.cmd script from this blog post to install 4.5.2 or 4.6 on Azure Cloud Service when deploying but without any change in result: https://azure.microsoft.com/en-us/documentation/articles/cloud-services-dotnet-install-dotnet/
Are Cloud Services compatible with Azure 2.7?
-- UPDATE: Yes. Make sure you use .Net framework v4.5.1
Is the install.cmd script really needed when running in local debug mode? Both 4.5.2 and 4.6 should already be installed, right?
Anyone else experiencing problems with this?
Any help or hints on how to get Cloud Services to work with Windows10, Vs2015 and Azure 2.7 are greatly appriciated!
Here is a repo with a sample project: https://www.dropbox.com/s/ie7jcn932nsddio/CloudServiceRepo.zip?dl=0

If your underlying cause is the same as mine, I have a workaround (if not an actual cause and solution)
Add this under the runtime -> assemblyBinding section of the app.config for your worker role:
<dependentAssembly>
<assemblyIdentity name="Microsoft.WindowsAzure.Diagnostics" publicKeyToken="31bf3856ad364e35" culture="neutral" />
<bindingRedirect oldVersion="0.0.0.0-2.7.0.0" newVersion="2.7.0.0" />
</dependentAssembly>
Here's how I arrived at this. In VS2015 with SDK 2.7, I created a brand-new, empty cloud service. I pulled in my existing worker role, which was created with SDK 2.6 and upgraded to 2.7. This time, I got a new error complaining that it could not find Microsoft.WindowsAzure.Diagnostics version 2.6. In my worker role, my assembly reference is for version 2.7, not 2.6. So, something in the worker role (which I cannot find or understand) still wants version 2.6 of this assembly. Bad upgrade by the SDK? Dunno. Anyway, by adding this entry in the app.config, I force it to use version 2.7 instead.
I don't know why I get a different (and more accurate) error message when I create a new cloud service, versus using the old one. I also don't know what this has to do with the original "WaitHandle" error, but perhaps that was a red-herring, and the original problem has always been a version mismatch? I'd like to know what caused this problem and what the proper long-term solution is, but I'll settle for this workaround for now.
Good luck, I hope this works for you as it did for me.