I have installed Visual Studio and Azure SDK v1.3.
All I am trying to do is follow the steps on this tutorial Task5 step 4
http://msdn.microsoft.com/en-us/gg502180 .
The only one I can not see is "New Virtual Machine Role"
I am new to azure, does anyone know what I am missing?
It's currently in beta and you have to request access before you can access the feature.
Log into the Azure portal
On the left there is a folders labeled Beta Programs, click that.
You'll see a list of available betas. (VM Role should be here)
Select it and hit join "(or request, I can't remember the exact word)
Once approved (not sure how long it takes anymore, prob pretty quick) you'll have the VM Images folder and can follow that tutorial.
The answer is on an e-mail sent to you by wacc#microsoft.com.
"After you have installed the Windows Azure Tools, please run this additional script to enable the VM Role features in the Visual Studio development environment: 32-bit or 64-bit."
Select your environment and run the script.
Related
I have installed UiPath Cloud Studio version 21.10.5 with advanced settings in service mode on a Azure windows instance using a service account per the instructions in the link below:
https://docs.uipath.com/installation-and-upgrade/docs/installing-the-robot
We are using Cloud orchestrator. I see that the UiPath Robot service is correctly installed and running as the Local System account as it should.
When I configure and use a robot account on this instance (03) with a machine template key that works on another instance (02), the unattended robot job does not run. I specify the robot account, the machine, the hostname correctly in the process start page. I have the non-production license applied to the machine and the job correctly. It just sits in the Pending status and does not run in Cloud Orchestrator tenant.
The same test job runs on another second instance(02) with the Studio Cloud 21.10.5 with the unattended robot option. The second host has the same machine key of the same machine template.
Is this a bug? Or is the Studio with service mode not supposed to work?
I am aware that there is the alternate option to use unattended robot install option with advanced settings and choose to install studio. I have not tried this yet. Has anyone else? Is this option supposed to work better with the unattended and attended robots and studio for development?
I'd like to know before we go too far down this path or try the alternate install.
Our setup works separately with studio on 1 instance (01) and automation developer with the user mode and unattended robot on the second instance (02) with the unattended robot setup.
We'd like to see if the Studio development and the unattended robot can work on the one instance. This is what I am trying on a third instance (03) to see if we can use 1 instance for both development setup and unattended robot with a service account.
Thanks for all the help.
The issue was that 1 non prod license can be used only on 1 host not 2 hosts for the same machine template. If using 2 hosts and 1 license, then whichever host connects to the machine first and acquires the license works and other does not.
To avoid this, we can go under tenant -> License -> see more -> disable the license on the host we are not running the unattended bot on and enable the license for the host we are running the unattended bot on. This worked.
2 robot accounts on the same host will work with 1 license. That is why I did not run into this on dev 02 with 2 robot accounts.
Per UiPath support separate studio and robot host and combined studio and unattended robot on 1 host work for development purpose. If combined, we may run into performance issue and need to keep an eye on memory.
Hope this helps someone.
I wrote a App for my family/friends and now we would like deploy it on or PCs. Publishing it in the store is not an option and not everyone has an Widows Live account. Sideloading isn't an option, because we do not own a Enterprise edition.
I found only the three already described ways. Either by publishing it in the store, using the development tools or having the enterprise edition.
Is there a fourth way to deploy a Windows UWP App without using the Windows Store or the need to install a developer certificate? If not, is there a possibility that something similar will be possible in the future?
The Windows 10 Deployment Tool looks like the thing I'm looking for, but i seems to be for mobile phones, or am i wrong?
The future is now! The process is easier on Windows 10 and the linked questions aren't relevant to that version. On Windows 10 users can enable developer mode or side loading in system settings on the "Update & security" page, in the for developers section.
See https://msdn.microsoft.com/en-us/library/windows/apps/dn706236.aspx
now with Windows 10 Anniversary update, you could just double click *.appxbundle file to install
Steps:
create your package, select no, when prompt "Do you want to build packages to upload to Windows Store?"
go to the package folder, double click *.cer, and install the certificate to Trusted Root Certification Authorities
double click *.appxbundle to install
Client OS Requirement: Win10 14393
UWP Target SDK: 14393
UWP Min SDK: 14393
On the target device, open the test folder. For example, C:\Projects\MyApp\MyApp\AppPackages\MyApp_1.0.2.0_Test
Right-click on the Add-AppDevPackage.ps1 file, then choose Run with PowerShell and follow the prompts.
Click the Start button and then type the name of your app to launch it.
I have a problem with a Windows 8.1 app that I want to deploy by sideloading.
I installed InstallShield premier to test it's feature, and generated an installation package that contains appx file and a test certificate file created by visual studio (associated in installshield project properties).
I need to enable app distribution in group policy settings to install.
After app correctly installs on system, i found it in start menu, but when i try to run the app, windows shows a popup that says "there is a problem with this app, contact administrator".
Target system is a Windows 8.1 Pro 32 bit PC.
Id there any other settings that I must enable on target system before install the app with InstallShield?
Thanks
There are multiple requirements for sideloading to work, documented on technet, which I've summarized here:
Activate the sideloading product key on the device OR join the device to an Active Directory domain (except for certain embedded devices which do not require either of these).
Enable the Allow all trusted applications to install Group Policy setting.
Since you don't mention it, I'm going to guess that your machine has neither the sideloading product key nor a domain membership (nor is it one of the special embedded cases), so that's where I'd start.
For more troubleshooting ideas, see some blogs like Sideloading Store Apps to Windows 8.1 Devices or How Do I Deploy a Windows 8 App to Another Device for Testing?
I think I misunderstood the whole Azure development concept. I thought I could run the Visual Studio IDE within Internet Explorer or something along those lines.
You can, but you'll use an RDP client (like mstsc.exe) instead of internet explorer. You can create a Virtual Machine in Azure that has visual studio installed on it and develop on that VM. There are a number of images already in the platform that support this scenario if you're an MSDN subscriber, I believe.
Even if you're not an MSDN subscriber, you can create a VM and set it up for development yourself. Then you can use your remote desktop client to log into that machine from anywhere and develop on it instead of your local box. This isn't limited to a Window dev env't either, of course.
I use this in scenarios where I have a constrained laptop but good connectivity and a desire to get some work done. You could use this to develop with a full IDE from a Surface RT, e.g. :)
I think I misunderstanded the whole Azure development concept, I
thought I could run Visual Studio IDE within Internet Explorer or
something
Azure is a web hosting environment in a nutshell. I think you are talking about Visual Studio Online in which you can run VS IDE inside browser.
Once you finish writing code in Visual Studio Online, you can deploy it to Azure.
Visual-Studio-Online-Monaco
channel9 - Visual Studio Online Monaco
I have a web application asp.net to deploy to Windows Azure. I try to run it on local first. But when debugging, I catch this error from VS2010:
"There was an error attaching the debugger to the IIS worker process
for URL 'http://127.255.0.0:82/' for role instance
'deployment16(6).WindowsAzureProject2.WebApplication3_IN_0'.
Unable to start debugging on the web server ......."
I've search so hard to find the solution for this problem but there's nothing seems work for me. I'm a newbie in Windows Azure, it's really a big trouble with me.
I had similar problem with Windows 8, debuging a cloud application with Visual Studio 2012 RTM and Azure SDK 1.71, when trying to launch the application into the compute emulator. It was a very simple app, but I used Azure diagnostics. At the end these are two things I have changed that have work for me, both turning on Windows 8 features (so go to Win8 and open 'Turn Windows Features On/Off'.
Activate the checkboxes for:
Internet Information Services Hostable Web Core
Internet Information Services > World Wide Web Services > Application Development Features > ASP.NET 4.5
Internet Information Services > World Wide Web Services > Health and Diagnostics > Tracing
Internet Information Services > Web Management Tools > IIS Management Scripts and Tools
That worked for me, it makes sense, as I'm using Visual Studio 2012 and trying to get some trace information using diagnostics in Azure.
I hope this will work for you or give some tip about the problem. In the case of being useful information, remember to vote as response or as value tip.
Thanks,
Mike
This usually happens when there's a problem with the project to be deployed to the emulator (WindowsAzureProject2 in your case).
Try the following:
Check %UserProfile%\AppData\Local\dftmp\IISConfiguratorLogs\IISConfigurator.log file for the error messages. See more details in this answer.
Make sure your project can be started without the emulator. It's a web project, so just try to start it as a regular web project. Or publish it to the separate folder and try to create a website in IIS of it.
Check your *.csdef and *.cscfg files to make sure all the configuration is correct.
Make sure that the build output of your project is not empty. You can do this by going to IIS, find the site with the name similar to deployment16(6).WindowsAzureProject2.WebApplication3_IN_0, right click --> Explore.... Make sure that this folder is not empty and contains all the files required to start a web project successfully.
BTW, there's a similar question: Debugger can't connect when starting local azure project
Follow step 11 from http://www.microsoft.com/en-us/download/details.aspx?id=35448. Worked for me on Windows 8 with Oct 2012 SDk
I just have today the same problem trying to Debug locally with Azure Storage Emulator in Windows 7. So in the Azure project properties, in Web tab, I checked the radio button 'Use IIS Express' and it debugged without problem. I hope this helps someone.
I encountered this exact same problem when I upgraded an existing Azure solution to the Azure SDK 2.1. After some hunting around I uncovered that the upgrade had automatically set the "Local Development Server" setting to "Use IIS Web Server".
Changing the "Local Development Server" setting to "Use IIS Express" fixed the problem immediately.
To access this setting right-click the Azure cloud project file in your solution, select the "Properties" option, tab down to "Web" and you'll see the following setup.
Also, make sure you run Visual Studio as administrator
Please check the version of emulator you have installed. If your code is created in older sdk and you have a new emulator installed it will give you this error.
Check the version of Azure APIs in your project, go to Project > references and right click on Azure dlls to check the version, same sdk version must be installed on the system, higher are optional as azure 2.x are not backward compatible.