I never notests this but if you create a new asp.net MVC website in visual studio you get full azure integration without knowing it. Turns out all of my applications, while hosted on my own server, are logging everything they do with Azure.
If I remove all azure dependencies from my project it won't build anymore. Is there a way to remove this feature from my asp.net project template? I really don't like this, for one, my inbox is exploding with "Data collection for .... has reached it's daily cap" emails and two, I feel violated in my privacy, why does Microsoft have know everthing of my projects?
Sorry for the possible duplicate question, but Google really isn't my friend on this one.
Actually, when you create a new project with default options you don't get any Azure integrations.
If your application is with Azure AD authentication, you should disable this when creating the new project.
If your application is doing logging on Azure, you can disable Application Insights.
Related
So I'm trying to deploy a test site to Azure.
The site has a database which was built in SQL server management studios, then I used ADO.NET Entity Data model to import the database into visual studios. Then I just used scaffolding to create CRUD operations.
How do I deploy this web app to Azure?
I used a database first so I'm not sure if that's a problem
I've tried following some tutorials but they seem to have different UI
eg. https://learn.microsoft.com/en-us/aspnet/mvc/overview/getting-started/database-first-development/publish-to-azure
First you want to go into Tools in your nav menu and check for 'Get Tools And Features'. Make sure you have Azure tools installed, and from there you'll be able to access the Azure menu to publish your web app directly from Visual Studio. You can also do this in VS Code, however you'll need the official Azure extension from Microsoft.
Let me start with telling that I'm not a Microsoft Dynamics CRM specialist. I only have experience with developing .NET solutions without CRM or SharePoint and some experience how to use continues deployment of TFS to release custom applications. But for a current assignment I start with developing for Microsoft Dynamics CRM and I'm not alone.
Here we work with 2 scrum teams. Both have their own Microsoft Dynamics CRM 2016 environment and we use TFS to save our source code. Only source code, no configuration of CRM. When we release software, we need to manually merge the CRM configurations into a third environment (integration environment). This takes a lot of time and everything needs to be tested again.
I've searched on the internet and find a lot of content about customizing CRM but not how to work with multiple teams and get an automatic release pipeline for the changes both in code as in CRM.
Does anyone knows what the best practices is to develop a CRM solution with multiple teams and how to make a continues release pipeline to get the C# code and the CRM configuration automatically to the test, acceptation and production environments?
What I have done was to use the solution packager. The scrum teams would develop against their CRM instances and in a specific solutions.
They can then (either automatically using scripts and the CRM API or manually) export the solution and extract it to a version control friendly format.
This can then be committed to the version control system and then (using an automated build) get repackaged and versioned and ultimately deployed to a integration CRM instance as a managed package.
The use of managed vs un-managed packages is a bit more lengthy topic though
Currently I have MVC2 web application(on going). If I'm to use Azure PaaS (Platform as a Service), Can I use the existing project. Or should I create new project (using Cloud service project template)? Can it be migrated? And what kind of effort will it take for migration? Or should I rewrite the entire application with new project template?
You don't have to rewrite the project itself, you can simply add another project to your solution (which is a cloud project) and then point it to your other project in the associated definitions.
This is a useful technique when you already have existing projects that you want to migrate to Azure.
Not sure if this would work with MVC 2 web application but you can simply try to convert the web application to Cloud Services project by right clicking on your project in Visual Studio (I used VS 2013), then Convert context menu and then selecting Convert to Microsoft Azure Cloud Service Project.
I have a solution with multiple C# projects linked to a Website (File => New => Web Site).
I can use the continuous integration for all the C# project for now.
I would like to try the website from a different solution just for testing:
I would like to know if the modification of an aspx or aspx.cs file will
rebuild all the solution/project or just push the file which was
modified on Azure.
It seams that the website will be rebuild, or will try to rebuild.
Here is my website test solution
and my Build Definition file :
So my question is, is it possible to integrate a website to a continuous integration system ? (TFS 2012)
If it's possible, What did I miss on the basic configuration ?(I didn't need any specific configuration for a WebApp project or a C# project)
I might need to build some files on the website (App_Code folder), But I would keep the possibility to deploy only the modified files (aspx, aspx.cs) without rebuild all the website and push everything on the server.
Let me know if you need any further information
There is an article here Continuous Deployment di Asp.Net web sites con TFS Build. It is in italian, but I think you may get the core using Bing/Google translator.
I'm trying to set up a TFS server for our small dev team, and since this is fairly new to me I have a couple of questions.
1) We are developing ASP.Net websites for internal use (intranet etc), these websites currently are not saved with visual studio solutions, they get saved basically as they are on the server and we just update them using Visual Studio by doing file > open website.
So my first question is should I save these as solutions in TFS? What would the benefit of this be?
Im coming from a background of developing WPF applications and have always seen everything saved with a solution in TFS.
2) What should we store in our TFS repository (and what should we exclude)?
At the moment I am storing source code & Documentation but is it really appropriate to store things like installers for VS plugins / small applications or should this kind of thing all be placed on a server someplace?
So my first question is should I save these as solutions in TFS? What
Yes, you could create a solution containing the different ASP.NET web applications.
would the benefit of this be?
Your source code will be version controlled
What should we store in our TFS repository
Source code, third party assemblies that your ASP.NET applications might require, script files, basically everything that allow to get your site up and running. Documentation should also be stored along with the project. Same stands for installers (the source code only, not the MSI) if those installers allow to deploy the ASP.NET application on the live servers.
and what should we exclude
Compiled assemblies, but they are automatically excluded by TFS anyway.