I have had a difficulty to add credentials and deploy any asp.net application. I have created account and application in the google cloud platform but when i have tried to add windows credentials in visual studio(2017) it has shown this error. It has shown it after the program asking me to reset the password for the specific username. What could be the problem?
The error is that your system isn't finding the "gcloud" command, which is part of the Google Cloud SDK.
Install the Cloud SDK.
Ensure that the gcloud command is added to your system's PATH environment variable. If you use the interactive installer this last step should be done for you.
Restart your system or IDE if it isn't picking up the change after installing the SDK. If it still isn't finding the application, you might need to manually edit your environment variable or point your IDE to the specific SDK location.
Related
Unlike the test tool for Windows 10, which is part of the Windows 10 SDK, Microsoft went out of their way to make the certification tool for Windows Server 2016 complicated.
I installed my test application and specified the path to the Inno Setup installer, off the Downloads folder, and specified the location of the binary files, namely the Program Files location, and the screen shown, I specified the process name, basically the executable file name. At least System Internal's Process Monitor utility said that was the name.
As you can see, I got thrown an error.
Log Time: 12/04/2018 08:57:21
MethodName:: ApplicationRunningViewModel.VerifyApplication
Message:
No running application's process found after your application installation.
==================================================================
Log Time: 12/04/2018 08:57:58
MethodName:: ApplicationRunningViewModel.VerifyAppProcess
Message:
Process not found in snapshot file.
==================================================================
How do I resolve the error? Basically, how is the steps to use this test tool?
Background:
I had previously certified my application for Windows 10 in the Windows Platform Ready / Winqual area of Microsoft and obtained the Microsoft Gold Application Development competency.
I was expecting to simply pay the yearly extortion fee, $5400, when I logged into the portal, saw the new redesigned Partner Center, and went to the Competency Summary section, where I saw the message that I am in danger to lose the competency. Microsoft apparently did away application certification based competencies for Application Development. Talking to MS external support, I was told what I already saw on my own that the Silver ISV is the only path forward testing against Windows Server 2016. My attempts to talk to a real Microsoft employee or find a real solution failed miserably. I think talking to Google is easier. I hope that MS straightens things out for next year. By the way, the Platform Ready / WinQual area disappeared as well as all certifications.
That brings me to my question. I am trying to use the Windows Server 2016 test tool (2019 was not available last week for download, hence 2016).
I already installed the application. It works fine on Windows Server 2016, just Microsoft did not make application verification easy.
How do I resolve this error? What piece of information does it want and how do I obtain it?
I found the same error while testing my application using the Certification Test Tool 1.0 for Windows Server for Windows Server 2019.
I just changed the sequence of the test. I did launch the tool and then installed my application. If you cancel the test your application must be reinstalled in order for the test tool to recognize your process. Everything worked as expected
I got another error while using the Certification Test Tool Preview for Windows Server 2016. He couldn't validate my signed assemblies because the tool verify the aseemblies signature usign the signtool.exe instead of sn.exe. If you signed your assemblies using the sn.exe, neither of the test tools for Windows server 2016 & 2019 will validate your signed assemblies. I had to check the log file generated by the test tool and sign the assemblies manually using the signtool.exe.
I hope this information help someone havign the same issues.
Greetings
When going to publish my Mobile Service Backend there is supposed to be an option that says "Microsoft Azure App Service" but instead I get two other options: "Microsoft Azure Web Apps" & "Microsoft Azure API Apps (Preview)".
The Web Apps option identifies my service plan and SQL server but wants me to create a new mobile web app url which I already have.
Neither of these show my App Service I have already created. Is it because I don't have Azure SDK v2.9 or higher (as stated by the online resource I'm using)? When going into the NuGet Packages and it only has v2.0 for Microsoft.Windows.Azure.Server and no higher version
Anybody know how to get the higher SDK without going through VS 2015 or any other options?
According to your description, I suggest you could firstly check the existing of the mobile service resource in the VS2015 server explorer.
You could open it in the view --> server explorer.
Anybody know how to get the higher SDK without going through VS 2015 or any other options?
If this resource is existing, but the publish windows doesn't show this resource.
I suggest you could update your azure SDK(the newest is 3.0.1), you could install it in this link.
Besides, I suggest you could check you have created mobile service not web app service.
I know that I in the past was able to find the code used for the visual studio part of the azure sdk.
Need to see how visual studio selects certificate and generate remote access passwords when creating cloud services. But I have had no luck searching around in https://github.com/WindowsAzure for it
Need the c# code that selects a certificate and uploads it to azure for the deployment.
Not sure where the actual SDK source is, but I've posted this solution on SO and my blog for Securing Azure ServiceConfiguration values for Enterprise Deployment. Writing the code to encrypt/decrypt is trivial and full examples are provided. Adding the certificate to a deployment is also easy - just add it to to role settings. Depending on which SDK you are using, you may have to run with elevated privledges.
I'm developing a Windows Azure Web Role. Everything is fine, but in order to launch the site I need to run it from visual studio each and every time and let it start the emulator with the site.
What I would like to do is some how run it independently of visual studio, use visual studio to develop and compile and just refresh the site (as if I was building a regular web project and was hosting it on my local IIS).
Is this possible with the Azure emulator?
Thanks
Yes. There could be a couple of options here. If your web site doesn't need access to the Azure role environment at all (meaning you aren't using RoleEnvironment anywhere in your code and you don't have dependent start up tasks, etc.) you can set it as the start up project and it will run under IIS (or IIS Express if you have that set) outside of the emulator. This is just like what you are used to. There could be some issues here if you need the actual emulated environment for some reason. If you are connecting to the Development storage you should still be okay as long as you ensure the storage emulator is already running (which you can manually start outside of studio either with the command line, or hit the start button and start typing "Windows Azure Storage Emulator - v2.2" until you see it as a choice). The storage emulator runs separate from the compute one and will be listening on the ports it is configured for.
The issue with not running the emulator if it is required is that you need to have the application packaged and deployed. You can directly use the csrun command line tool to spin up a deployment in the emulator. Mike Barlow did a post on it a few months ago: "How-to deploy application to Windows Azure Compute Emulator with CSRUN" Note that the article has you spin up something without VS open, but it still needed to be "packaged" and put in the referenced csx directory.
You may also want to look at the new Express Emulator which is supposed to be a little more stream lined, at least permissions wise, but I can't say if it is any faster or not. I'd consider it beta currently.
When I install my C# app in windows 7, UAC always shows. I'm not logged in as Administrator but I want my application to be installed without the UAC.
Can you give me ways on how to do it?
The UAC prompt shows for any number of reasons, none of which is "the code inside the exe calls function X or tries to write to place Y." These include:
the name contains setup, patch, update etc (eg setup21.exe) and there is no manifest
you embedded a manifest that asks for requireAdministrator. You would have done this on purpose in Visual Studio.
there is an external manifest (for NewApp.exe it would be NewApp.exe.manifest) in the same folder that asks for requireAdministrator. You would have done this on purpose too.
you have right-clicked the exe, and on the Properties Compatibility you have chosen to elevate it, or to run as XPSP2 which for 7 also elevates
someone in your company has applied a Group Policy that this installation app should run elevated (unlikely)
you once ran it, got a dialog from Windows saying "that may not have worked right" and agreed to try again with "recommended settings"
Do any of these seem likely? If so, correct them and see if the UAC prompt goes away.
Single Package Authoring link text
You'll want to use Windows Installer / Windows Installer XML to make this install behave the way you request.
If you want to install an app without UAC then you can only touch folders that the currently logged in user can write to. Google Chrome does this--it installs the entire application to the user's local application data folder.
It's very non-standard and I would argue MS should prohibit running code from this location, but it's a working solution to requiring administrator/UAC access to install applications.
Incidentally, Google Chrome more recently made a traditional installer available so one user can install it to be used by all users on the computer.
If you want your application to be installed without triggering the UAC, install to %APPDATA% (instead of installing to %ProgramFiles%) and write to the HKCU hive only in the registry (i.e. don't try to write to HKLM, HKCR, etc.)