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
Related
I have an existing Web Project. I clicked "Add Application Insights Telemetry to Project" and at one point in the process it threw an error like '[...] failed to initialize the powershell host [...]'. Then I tried a few things according to Google searches.
There is no ApplicationInsights.config in the project, nor is the Microsoft.ApplicationInsights.Telemetry.Services referenced.
Now there is no 'Add Application Insights Telemetry to Project' option to be found anywhere. I even tried to re-install the Application Insights extension.
I tried to roll back any changes via git, but without luck.
Non of my teammates see the 'Add Application Insights Telemetry to Project' option in VS. (We're all using Visual Studio Ultimate 2013 Update 4)
In case I can't get this to work, is there a way to manually set this up?
Manually, you can add the nuget package yourself (the web one is: http://www.nuget.org/packages/Microsoft.ApplicationInsights.Web)
and then manually create an application insights resource on the Azure portal (http://portal.azure.com), and then take the instrumentation key for your new resource, and paste it into the ApplicationInsights.config file that the nuget package installed into your project.
The AI VSIX adds a GUI on top of those steps. (can help you fix whatever's wrong with the vsix i'd rather have you do that first, though!)
I found that this was related to the ProjectTypeGuids being missing from my csproj files.
In VS2015 the following ProjectTypeGuids needed to be present:
<ProjectTypeGuids>{349c5851-65df-11da-9384-00065b846f21};{fae04ec0-301f-11d3-bf4b-00c04f79efbc}</ProjectTypeGuids>
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'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.
I have a com interop dll (zkemkeeper.dll) that i have to register and use, i wonder how can i deploy that to the SharePoint server using SharePoint package?
You cannot deploy COM or COM Interop DLL to SP farm by SP solution. You need to install the component on every SP server in the farm by other means.
Create an MSI installer to be executed on every machine. MSI can be rolled out automatically too.
Provide a PowerShell script to be executed on every machine. PowerShell can be run remotely too.
Deploy a timer job with your solution that would be executed after the installation automatically or manually and would write to the registry the necessary COM stuff.
The first two options are my favourite because they shouldn't cause technical problems at the customer. The third one appears to promise installation without visiting every machine but the Timer Service user identity would need permission to write to the local registry which may not always be granted; and you'd have to resort to 1. or 2. anyway.
You should think about switching over to ASP.NET or .NET components on the long term. There are many components available in pure .NET that can be deployed by SP solutions. You can also consider pure HTML/JavaScript controls. I would probably go for the option 1. and invest the saved time to other architecture without the COM Interop.
--- Ferda
If you are using Sharepoint 2010, see How to: Add and Remove Additional Assemblies.
See also:
Deploying custom dll's in SharePoint 2010
Visual Studio - SharePoint 2010 - Include Assembly > Quick Question
Include 3rd party dll in the Sharepoint project while packaging the wsp
visual studio does not copy assembly into gac
How to install a WSP that has dependant assemblies?
Interop.zkemkeeper.dll regsvr32 error or InitializeComponent
Then you need done the step following:
Go to the website: http://www.zktechnology.com
Download ->Software Download->ZK Access for C3 panels
Extract files
Install
Open visual studio -> Solution Project->references-> Add Interop.zkemkeeper.dll
Good luck
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.