I am trying to create a new Azure Resource Group Project for Creating a Logic Apps Solution in Visual Studio 2015 however I am facing the below error mentioned in the Screenshot.
It seems a issue caused by visual studio instead of azure. You may have a corrupt install and depending on the order that dlls are loaded determines whether you see the error or not.
This is a workaround in the similar issue that you could refer to.
The workaround - which does not always work right away - is to Sign out of Visual Studio (This takes 2 attempts to sign out and remove the credentials). Then reboot the PC. Once logged into WIndows, launch Visual Studio - DO NOT SIGN IN. Open the solution, right click on the Deployment project; which may or may not trigger the same dialog error. If the deployment dialog is display, then i can add account and deploy. Otherwise, i must turn off the PC and try again, and again, and again, until it starts working.
I recommend you can try the workaround if necessary.Then you could report the problem and ask the Microsoft visual studio support for help.
Related
I am currently developing an Azure Logic App. This is very straight-forward from portal, but I need to use Visual Studio as an IDE for this. I have followed all the steps mentioned in https://azure.microsoft.com/en-in/documentation/articles/app-service-logic-deploy-from-vs/ article, but when I try to do right-click "<>.json" and say "Open in Logic App Designer", the Visual Studio crashes everytime.
Could anyone please assist on the same?
Thanks
I has a similar issue, I found I had to install the Azure Logic Apps Tools (https://marketplace.visualstudio.com/items?itemName=VinaySinghMSFT.AzureLogicAppsToolsforVisualStudio), restart Visual Studio and then create the Azure Resource Group project for it to work.
The project that I had generated without the tool installed did not work (ever).
I'm using the Azure SDK 2.9.6, Visual Studio 2015 update 3
Are you currently signed into Visual Studio with an account containing valid Azure subscriptions/currently has strong internet connectivity? That is known to cause editing issues before.
If that does not solve your problem, we have enabled logging feature in our most recent update (ver 1.0.0):
a. Open developer command prompt for VS2015
b. Run following command to start VS with activity logging enabled.
devenv.exe /log
c. Repro the issue in this instance and close it.
d. You can find the activity log at location :
%APPDATA%\Microsoft\VisualStudio\14.0\ActivityLog.xml
e. Please send us this file to us.
If you can share the logs with logicappsbug#microsoft.com, we can further assist you on this specific problem.
Thanks,
Max
My need
Currently I have to open Visual Studio to make a get latest or a commit pending changes.
I want to do that the same way with TortoiseSVN right in Windows Explorer.
What I have tried
I made google research and comes down to using the tool called TFS 2012 Power Tools
Someone also mentioned about this issue here
Though after installed, I got nothing working as espected. Wondering did I do wrong then...
I'm using Windows 8.1 and Visual Studio 2012 Web Express.
Question
How should I do to install it properly and get it work after all then?
Assuming that when you installed the power tools you enabled shell integration and then logged out/back in to active them, then you need to do a few things:
Do an initial 'get' from TFS using Visual Studio Team Explorer and make a note of your workspace folder.
In Windows Explorer, right click that workspace folder. You should see the context menu items appear.
Most people having trouble with the context menu appearing have forgotten that to log out and log back in, as Windows Explorer needs to be restarted to pick up the new shell extension.
Our team has been having quite a lot of trouble with Visual Studio's publish feature. We use TFS and are all running VS 2012 ultimate. It works fine when only one person is involved in a project, but when we get many people inside one project, the publish profiles get off and Visual Studio reports a successful publish even when all files haven't been copied up. I've read all the SO questions about why this happens and I understand that TFS adds the publish profiles to the source control automatically. If we create a new publish profile and republish, everything works. But this is not sustainable. I can't prevent VS from automatically adding the publish profiles to TFS (if we could, I think this would solve the problem) so I'm now looking for better ways to publish an application to a web server. Is there a better tool out there to publish web applications or do I need to write my own VS extension?
Per this question (https://stackoverflow.com/a/12393154)
The temporary answer seems to be to change your settings from release to debug, save, then switch it back. This causes the pubxml.user file to be rebuilt, which is actually the problem.
I am getting an Exception when I am trying debug my application on Emulator (Web Role).
you can see exception by clicking following link
Configuration which I am using Windows 7 pro, VS 2012 Pro, Azure SDK 1.8
Hope it might help others.
I Also had the similar problem and I restarted PC and **Run Visual Studio as Administrator**.
And let Visual Studio start the emulator with same privilege resolved the issue.
I was using Visual 2013 and Web API application under IIS Express.
Do you have IIS added? Most likely it's already installed but you've to enable it via Add Windows Compoenents on Control Panel...
I had this same issue all of a sudden, luckly I remember changing the ServiceDefinition.csdef file. I rolled this back to an earlier version and the debugger ran again correctly. The only thing I changed in the 'broken' version was instance size from small to medium.
Go to visual studio installer(search it from window's start)
and update the visual studio.
After updating, hit modify
button, after that on right side you will find a box named
debug (or something like that), select that box
Then hit install.
Restart your visual studio and debugger will start working.
In my case it worked perfectly.
I'm trying to move a solution I have over to Visual Studio 2012 and one of the project types is .vdproj.
According to this link this project type is not supported in Visual Studio 2012:
MSDN says they recommend that you use InstallShield Limited Edition for Visual Studio.
The problem is, when I open up my solution in VS2012 and try to add a new "Enable InstallShield Limited Edition" project to my solution, I get an error message saying:
Creating project 'test'...project creation failed.
Why might I not be able to add a project of this type to my solution?
If I make a new empty solution I can't make an InstallShield project it in either.
I'm going to try to download InstallShield limited edition and see if it does anything.
I tried out that InstallShield download, and it added two extra project types, but I'm unable to create either of them. I'm able to add normal website projects to my solutions just fine, but not deployment projects.
The installer was named the same, but this one prompted me to re-start. After re-starting I was able to add an InstallShield project, but it gets created in its own solution. So, it looks like now I have to figure out how to use it, and I'll be good to go.
It's looking like the limited edition doesn't have support to install Windows services.
This will probably be long and boring because there's lots of steps, but I'd like to write up how to move from a Windows service installer .vdproj to the new InstallShield LE that's available in Visual Studio 2012.
Step 1: Create a merge module (.msm)
Follow the steps of this guide.
Notes:
You will need to install WiX 3.6 and isWiX
The latest release of IsWiX doesn't enable the Tools menu item in Visual Studio 2012. Edit the file: C:\ProgramData\Microsoft\MSEnvShared\AddIns\IsWiXAddin.Addin (XML) and clone the HostApplication element and update 10.0 to 11.0.
In step #8 of the guide, it references a code tab. This has been moved to the XML Editor item in the bottom of the left menu
I left the MergeRedirectFolder empty for my installation
Here is my isWix files view:
After you're done with the guide you should have an empty .wxs file that looks something like this:
Using the Component XML element pulled from here you should end up with a .wxs file that looks like this:
Hit build and you should now have a .msm file.
Step 2: Adding merge module to InstallShield
Go though the wizard to setup the basic install information like company and version information.
Find the redistributables view in ISLE. Right click the list and select browse for module. After your module is found and added, right click the modules and select properties. Set the destination folder drop down to INSTALLDIR. I had to set mine to the lowest level folder I created for my install path, so you might have to experiment a bit.
Build Project, and test on virtual machine
Redistributables Screen
If you're getting errors about the path being too long you might need to change the release location to something close to the root.
Here's a list of all the build errors for reference.
Now you should be able to run your installer and have it install/start a Windows service. A lot more work than .MSI files, we got it to generate in Visual Studio 2010, but overall it was not too bad.
While there is no easy or truly supported solution for Visual Studio 2012, Visual Studio 2013 users can get an extension from Microsoft in the Visual Studio Gallery.
I found this post which says you must download InstallShield first. It's a very confusing way to work. I suggest to vote up the post on the connect site and give them comments letting know how poor that is. They could at least give a more descriptive error http://connect.microsoft.com/VisualStudio/feedback/details/732196/project-creation-failed-for-installshield-limited-edition#tabs