I'm trying to log diagnostics into storage account.
Throw error
Nothing happens. No dialog box.
Any help will be greatly appreciated!
I would like to suggest you to check your csdef and cscfg files. If you can see any invalid configurations, they may cause issues in Visual Studio UI. In addition, everything we do in the Visual Studio UI can also be done by manually editing csdef/cscfg files. So if you can’t get this particular feature to work in Visual Studio, you can also manually modify the connection string. Please refer to http://msdn.microsoft.com/en-us/library/windowsazure/ee758697.aspx for more information.
Best Regards,
Ming Xu.
Sounds like there was a problem installing the Azure SDK. Have you used this before and it just started happening or is this the first time you tried to do this?
I would say uninstall/reinstall the SDK and Azure VS Tools.
Related
I have installed Visual Studio Code (ver 1.14) on Windows 7, and added the extension Azure Policy (ver. 0.0.22). After signing-in into Azure Cloud by using the Visual Studio Code Azure Account extension, I try to update the panel in the upper left side of the window in which the resources available in my subscription are listed, unfortunately an error message pops up which says:
command 'azureResource.refreshTree' not found
Does anyone has experienced same problem? Any idea about the root cause and how to solve it?
Thanks for any help
The problem was there for a few days till I rebooted Windows. I don't know if this was the real solution of the problem, but it worked for me.
Crash on Azure publish from Visual Studio. The same thing happens in previous versions of Visual Studio, but in the past I've been able to work around the bug by clearing the appdata and if necessary resorting to resetting user settings per the responses to this question about a VS2015 issue.
Azure publish has been working up to now in 2017. Suddenly I am getting the dreaded null reference, and this time clearing the aforementioned data has not helped:
Restarted Visual Studio, restarted machine, cleared data a second time including both roaming and local appdata, all to no avail.
Just for others searching, in my case the issue was that I had previously disabled the "Microsoft VisualStudio Managed Publish" extension in VS2017 (probably in an attempt to get VS to be more responsive). To re-enable it, go to Tools > Extensions and Updates, enable it, then restart VS:
Thank you for your sharing. I have the same case as you. I accidently disabled the "Microsoft VisualStudio Managed Publish" extension in VS2017. The publish menu even doesn't show up in .net core solution explorer. To re-enable it, go to Tools > Extensions and Updates, enable it, then restart VS.
Unchecking/unselecting the Application Insights in the Publish workflow of Visual Studio 2017 fix the error for me.
This can be caused by a validation error in the service definition and configuration files.
Even though the editor doesn't highlight any problems, and the build completes successfully, there can be errors in these files and they are not handled properly when you attempt to publish, giving the null reference error.
I encountered this after modifying the files per these steps to configure SSL. I really wasn't expecting that to be the culprit, but in desperation I was trying everything I could think of that might be causing the problem. As soon as I commented out the change to the <certificates> element, the null reference error went away, and the publish succeeded.
(I now need to work out why the steps for SSL configuration didn't work, perhaps due to a change introduced by VS2017, but that's another story.)
I was experiencing the same issue as the OP. I created a new DB Project and then compared the settings of the new DB Project with the DB Project that was causing the Null Reference Exception upon Build or Publish. I noticed that our output directory was redirected to a non-standard location. After deleting all the files in the bin folder, the Build and Publish started working. YMMV
I found a lot of answers around that -- so may be there are more than one -- but none worked for me.
On my system it worked again after removing the installations for ASP.NET and Azure and installing it newly .. --> evth is fine.
How do I enable IntelliTrace when I deploy an azure package from powershell using the command New-AzureDeployment?
Grant's blogpost pre-dates VS2012 where we added the powershell controls to IntelliTrace. (I'm the dev manager for IntelliTrace) This gives you more options in VS2012.
IntelliTrace is licensed such that you can collect data where ever you want with the new remote collector. You can only open those files in VS Ultimate however.
First you need to grab the standalone collector:
http://www.microsoft.com/en-us/download/details.aspx?id=30665
It will drop a cab folder that contains all the bits you need for collection including PowerShell.
You can now TS into your azure box, copy the bits down and then use these instructions to collect:
http://msdn.microsoft.com/en-us/library/vstudio/hh398365.aspx
I've not actually tried to add IntelliTrace with New-AzureDeployment but as the bits inside the cab file are xcopyable, I imagine you just need the IntelliTrace included bits in the package you are
deploying. Although this won't turn them on for collecting logs directly from the server explorer in VS. You would still need to use the powershell commands to control the collection. To get the control from the server explorer, you would want to do what bhavesh lad suggested.
Hope this helps.
I don't think this is supported as IntelliTrace comes only with VS ultimate edition. There are some work around which people has posted but not sure whether it will work... Here is that link: http://blogs.msdn.com/b/granth/archive/2011/02/20/intellitrace-for-azure-without-visual-studio.aspx
I'm happily in the middle of coding then I try to launch my app in debug mode but I get this error message.
Unable to activate Windows Store app
This app failed to launch because of an issue with its license
The app was launching fine a few minutes earlier so this came as a surprise. I tried restarting Visual Studio but doing so did not help.
I got the annoying "renew your developer license" dialog yesterday I think. It had renewed without issue.
How do I make this error message go away so i can debug my app?
Well, I got it working by deleting the main project's 'bin' and 'obj' folders. Cleaning and Rebuilding wasn't enough. Hope this answer saves someone else the few minutes of confusion I just experienced.
I recently had a similar issue. In my case I had to uninstall the re-install the app to get it working.
Hope this helps someone. Also, to find out further detail about why it failed, you can checkout the event logs:
Event Viewer > Applications and Services logs > Microsoft > Windows > Aps > Microsoft-Windows-TWinUI/Operational
There might be some more detail in there. In my case it was logged as an error event which said the app could not be launched because of a temporary issue with its license.
I just uninstalled the existing version of the app from the start screen, and then launched the app again from Visual Studio and it is launched just fine.
I think the reason behind this is because of renewing the license of Visual Studio and trying to launch an app that was installed when the previous license was active.
I see doing stuff with the bin and obj folders appears to be the accepted answer to this.
I fixed this issue by selecting the 'Uninstall and then re-install my package. All information about the application state is deleted.' check box under the Debug tab of the project properties. You can uncheck it once you've done it once for all future builds.
I haven't had any issue with this solution. Simple fix and you don't have to worry about someone doing something to folders that could cause bigger issues.
http://daxdude.blogspot.com/2013/04/c-error-unable-to-activate-windows.html
I've had this issue a few times now, most of the time deleting the Bin and Obj folders will clear the issue up (These folders are automatically generated during a project build so don't worry about deleting them)
I have found whilst debugging on a remote device (A tablet or phone) that Deleting these folders doesn't solve the problem though - in this case the best solution I have found is just to do a restart on the device I was remote debugging to.
Simple but it works!
I just cleaned my solution and re-started Visual Studio. That did the trick for me - and didn't involve hunting around for files to delete, so you might want to try that first.
go to BUILD-->Clean Solution and click and after its has been cleaned again go to BUILD-->Rebuild Solution. After it has successfully rebuilt your solution just deploy it(Ctrl+F5). This solved the problem for me.
When I start up VS 2012 RC I get the following loading error message:
The 'SqlStudio Profile Package' package did not load correctly.
The problem may have been caused by a configuration change or by the installation
of another extension. You can get more information by examining the file
'C:\Users\User\AppData\Roaming\Microsoft\VisualStudio\11.0\ActivityLog.xml'.
I also have SQL Server 2012 RTM installed.
What can I do to get rid of this warning?
Open Control Panel
Open Programs and Features
Locate all items named “Microsoft SQL Server 2012 Data-Tier App Framework"
Note: There might be up to 4 such instances all with the above name
Right click each of them and select Repair
That should solve this issue.
Janaka solution worked for me.
But if you do not want to lose your VS configuration, remove only the file :
Microsoft.VisualStudio.Default.cache
from the folder
%UserProfile%\AppData\Local\Microsoft\VisualStudio\11.0\ComponentModelCache
Hope it helps.
Remove the following folders.
C:\Users\UName\AppData\Roaming\Microsoft\VisualStudio\10.0
C:\Users\UName\AppData\Local\Microsoft\VisualStudio\10.0
See this
It turns out that (in my case), the Data Tools installer has a bug whereby you end up with a registry full of:
Microsoft Visual Studio 11.0Common7
...paths, when it should be:
Microsoft Visual Studio 11.0\Common7
Fixing all the values and keys fixes the problem (for me).
(ps: no other solution in this thread worked for me)
Just reinstall SQL Server Data Tools (SSDT)
I had to run VS as an administrator in order to clear this issue.
Problem: The 'SqlStudio Profile Package' package did not load correctly.
Proven Solution:
Removing Microsoft.VisualStudio.Default.Cache fixes the problem outlined above. It worked!