Does the web server built into Visual Studio 2010 (and earlier, but 2010 in particular), WebDev.WebServer.exe, support the HTTP verb PUT? If so, does it support it by default or does it require configuration? If it requires configuration, please describe how to configure it.
In Visual Studio 2010 at least, the Visual Studio Development Server web server does seem to support the HTTP PUT method.
I previously answered that it does not, but the URL for which I was submitting requests with the PUT method was incorrect. Once I corrected the URL the request was accepted without requiring any other changes to Visual Studio or the built-in web server settings.
Related
I am trying to set up a project in Visual Studio 2017 that does what I am already doing in Visual Studio Code.
I have is a typescript Web page which uses THREE for WebGL so it is client intensive. It needs to interface to a custom Web server running on localhost. For Visual Studio Code I open the Web site, set up the source maps and I can set breakpoints in the typescript for the Chrome debugger inside Visual Studio Code. A true IDE for typescript.
Here is what I have tried with Visual Studio 2017:
1- Open a Web Site. This is the same Web site that works in Visual Studio Code. I cannot get the typescript to build.
2- Create node.js typescript project. Typescript builds but I cannot connect to any Web server and see my code. I can only start up server.ts. In theory I can build a Web server in node.js but I need to connect to my custom Web server.
3- Set up a C# ASP project. I can build typescript and set breakpoints but the breakpoints are not hit.
The third option was recommended as a way to get typescript to compile but it builds C# DLL’s and doesn’t seem logical. I don’t remember whether I could attach to my custom Web server or not. This was in response to the disappearance of the typescript Web page from the templates on VS2017.
Visual Studio Code has its advantages but it is brittle. The breakpoints stop working sometimes and now I can’t get source maps to work. In theory this should all work perfectly on Visual Studio 2017 right?
We have a nuget feed set up on our Team Services account. With VS 2015, I can authenticate no problem, using the Microsoft login form.
With Visual Studio 2013, it pops up very generic authentication form, which keeps popping up no matter what I input to it. Has anyone else come across this? Any way around it?
Normally, I would just use 2015 to authenticate then 2013 would be fine. Unfortunately, I can't get 2015 to run on my pc anymore - so I need to make this work with 2013.
Authenticate to VSTS feed via "Nuget Package Manager" requires VS2015 Update1 and later just as the information mentioned in the page provided by Jack.
If you don't mind to store the credential in "Nuget.config" file, you could use Personal Access Token method which support all nuget client and easy to use. And Nuget Auth Helper is also a good method to do this.
I understand that browserlink uses SignalR to create an open connection to Visual Studio 2013. For an asp.net MVC application I am developing and testing in the latest firefox browser, the transport method used by the browser link connection is "longPolling".
I am curious why the transport method is not promoted to a WebSocket connection.
For the the BrowserLink feature to support WebSockets, you should be using Windows 8 or Windows Server 2012. You can get more details about this from this answer.
I opened a C# project that was created in VS 2010 SP, with VS 2013. A one-way conversion window appeared where I proceeded with the conversion.
Following warning message appeared
"Visual Studio needs to make non-functional changes to this project in order to enable the project to open in Visual Studio 2013, Visual Studio 2012, and Visual Studio 2010 SP1 without impacting project behavior."
when I run the application it gives the following error
Description: An error occurred while accessing the resources required to serve this request. The server may not be configured for access to the requested URL.
Error message 401.2.: Unauthorized: Logon failed due to server configuration. Verify that you have permission to view this directory or page based on the credentials you supplied and the authentication methods enabled on the Web server. Contact the Web server's administrator for additional assistance.
If I run the same app in VS 2010 it works fine.In VS 2013 upgraded the MVC3 to MVC 4 using these steps
http://www.asp.net/whitepapers/mvc4-release-notes#_Toc303253806
This solution worked for me, but depends on the type of security utilised by your application. I required Windows Authentication to be used as the application was running on our local intranet.
Anyway, my problem lay with the default IIS Express settings for running the app. These can be found in your default My Documents folder for the IISExpress\config folder and modify the applicationhost.config settings to your liking.
I have a custom SharePoint ASP.NET Web Service project.
I've setup it to debug as described in http://www.sharepoint-tips.com/2007/08/web-services-on-sharepoint-making-f5.html
it used to work as long as I was working with Visual Studio 2005.
but now I want to setup Visual Studio 2010 environment,
and I'm stuck trying to set 'Use Local IIS Web server' setting in VS, the error says: "The local IIS URL ... specified for web project ... has not been configured."
Tried in both: Windows2003 with MOSS 2007 and Windows 2008 with SharePoint server 2010. All the same.
What I'm missing? thanks in advance.
For Visual Studio 2010 and SharePoint 2010, F5 should work right out of the box. There's no need for any special tricks. Have a try without that outdated blog posting.