visual-studio

Bad Request – Invalid Hostname with Asp.net WebAPI project in Visual Studio 2013

by

I am running a very basic webAPI project in Visual Studio Pro 2013. It runs fine on localhost on my machine. I then try and go to a browser from a different machine and goto :57571 similiar to how i could point to rails apps by putting the servers ipaddress followed by the port number. I then get
Bad Request – Invalid Hostname HTTP Error 400. The request hostname is invalid.

Adding NUnit to the options for ASP.NET MVC test framework

by

I have nUnit installed. I have VS2008 Team Edition installed. I have ASP.Net MVC Preview 4 (Codeplex) installed. How do I make Visual Studio show me nUnit as a testing framework when creating a new MVC project? At this point I still only have the Microsoft Testing Framework as a choice. Update: I installed nUnit … Read more

How to rename an IIS Express website in Visual Studio 2012

by

I initially created a site in Webmatrix 2. I just called it website1. I’ve now been working on the site in Visual Studio 2012 and I would like to rename it. It doesn’t appear you can rename it directly, but in the .sln file there is a project entry which contains the string “website1”. I renamed it and re-started VS. The new name briefly displays but then gets overwritten with the original name. So now I have the .sln file with the new name and nowhere within the folders does it reference the old name – i’ve searched every file. But yet VS insists on calling the site website1. So i’m totally confused.

Element ‘system.webServer’ has invalid child element ‘rewrite’. Should I fix this, and how?

by

I have a number of rewrite rules for a lot of things that I did in IIS7, like removing trailing slashes, canonnical URLs, lowercase lettering, and such. IIS altered my web.config, and everything works fine on the website, like it should. But in the Visual Studio web.config, the opening <rewrite> statement is underlined in blue, and at the bottom of VS, it says that the element ‘system.webServer’ has invalid child element ‘rewrite’. But this is how IIS made it … I didn’t do this manually. Should I be concerned with this VS error, or should I just leave as be, since it’s working how it should work?