Sayed Ibrahim Hashimi has a computer engineering degree from the University of Florida. He works at Microsoft as a Senior Program Manager creating better .NET Core, and ASP.NET Core, development tools in Visual Studio.
We have just released the XDT transform engine on NuGet, with a license which allows you to redistribute the assembly with your own product. . If you are not familiar with XDT it is a XML transformation engine which drives our web.config transforms in Visual Studio. You can read more about XDT at here. You can now take a dependency on XDT and
Hi everyone Sayed here. I recently had a customer, Johan, contact me to help with some challenges regarding deployment automation. He had some very specific requirements, but he was able to automate the entire process. He has been kind enough to agree to write up his experience to share with everyone. His story is below. If you have any commen
Today I saw the following question on StackOverflow MSDeploy - Deploying Contents of a Folder to a Remote IIS Server and decided to write this post to answer the question.
Web Deploy (aka MSDeploy) uses a provider model and there are a good number of providers available out of the box. To give you an example of some of the providers; when syn
One of the most requested features of Visual Studio 2012 was the ability to open projects in both VS 2012 as well as VS 2010 (requires VS 2010 SP1). In case you haven’t heard we did implement that feature. You may be wondering how we were able to do this and how this may impact you.
If you open the .csproj/.vbproj for a Web Project created
Within the web publishing tools in Visual Studio there are a few places where we point to more resources. For example if you open a VS publish profile (.pubxml) file you will see a link in the comments pointing to http://go.microsoft.com/fwlink/?LinkID=208121.
Note: you can find the VS publish profiles in your web project under Properties\
The release of Visual Studio 2012 is right around the corner. If you’ve been following our blog/twitter then you may know that many of the Web related components of Visual Studio are now“out-of-band”, meaning that we can update them independently of Visual Studio itself. Because of this we are planning to ship updates a few times a year.