I want to implement a simple REST https server using visual studio 2017 (Windows 10). I used restbed with this code. But I got this error:
'rested::Http': HTTP client is deprecated; we will release a complimentary client framework at a future date.
I searched for a solution, but I found nothing.
Does anyone have any idea about this or any other suggestions for this problem?
Related
I maintain a legacy website written in asp classic that uses the MSXML2.XMLHTTP.6.0 DLL heavily and today all of a sudden it is throwing an error advising it can’t find the specified DLL. I did a check and the DLL is there and is registered correctly on the server.
Does anyone know if this DLL is no longer supported in Windows?
I have now resolved this (for now). The issue was with one of our API providers not the dll. Here was their response:
"We found a cipher that is not vulnerable and still supported on win 2012. Could you please test if you have an issue connecting using Win2008? We could leave it enabled for a longer period."
Enabling this cipher is what fixed the issue.
Recently I've had a problem where all my projects using ASP.Net Core with Swagger give a 403 error when trying to access them through a browser locally. This happened overnight and seems to effect all Swagger projetcs when run using IIS Express.
I have tried:
Different browsers (Firefox/Chrome/Edge)
Different operating systems
(Windows 10 / 7)
Different versions of Visual studio (2017 and 2017
preview)
Different machines
Going back to an old branch I know was
working
All give the same result. The issue doesn't seem to stop the API from working and when it is deployed to an Azure app service the Swagger UI appears with no issues. Any idea what the problem could be here?
Tried everything. Deploying same type of web project (Net.Core 1.1) with VS2015 at the very same location using exactly same parameters works without any problems.
Is there any known issue with release RC.4+26206?
This what my server log says:
IISWMSVC_AUTHORIZATION_SERVER_NOT_ALLOWED
Only Windows Administrators are allowed to connect using a server connection. Other users should use the 'Connect To Site or Application' task to be able to connect.
Process:WMSvc
User=sludr
Ok... Found a solution. Same reason as documented here: .net core web deploy requires admin permissions, so VS2017 requires right now a windows account of group Administrators to publish net core projects.
Hopefully this will be fixed soon.
Note: The official VS 2017 RTW still has this bug.
We have an ASP.Net website running under the 4.0 framework in IIS 7.5 on a Windows Server 2008 R2 box. A portion of the web site functionality utilizes WCF and has a "standardEndpoints" section in the web.config.
The website works fine and everything works fine if we want to use the IIS Management Console GUI to do things.
We would like to use powershell to make changes to the web.site but when we run "Set-WebConfigurationProperty" an error is generated indicating that the "standardEndpoints" section of the web.config can't be processed.
The hotfix referenced here is not the solution. The website works, the hotfix appears to be only for Server 2008 (not R2), and when you try to install it, it says "not applicable for this server".
We did discover by running $PSVersionTable that PowerShell was referencing version 2.0 of the CLR. We installed Powershell 3.0 and now Powershell is referencing version 4.0 of the CLR but the problem persists.
We are looking to see if there is a simple solution to this. I suspect we may not have the right version of the IIS management script dll but can't find a different one to use. If the solution gets to complicated, we will just wipe the server and start from scratch.
Thanks for any suggestions,
John
Is it possible to use SSL with Visual Studio Development Server (a.k.a. Web Application project)? I don't want to have to deploy IIS locally if possible. I'm running Windows 7.
NOTE: I've seen this (http://connect.microsoft.com/VisualStudio/feedback/details/354576/add-https-support-to-visual-studio-asp-net-development-server) but I was still hoping there was a workaround.
It cannot be done with VS 2008, so I've simply resorted to deploying my app to the local IIS as part of the start process with a generated cert.
We can use IIS Express with VS 2010 to develope and test web apps in SSL. Here is a complete article explaning how to use IIS Express and Visual Studion 2010 to develope websites in SSL
Working with SSL at Development Time is easier with IISExpress
Introducing IIS Express
this subject was covered here and it say's, you actually can't.
But you might take a look at this link, which might prove the contrary: (See link in comment, i'm not yet able to post more then 1 link per post ...doh)
Hope this helps.
It can be done in VS2010, I'm not sure if VS2008 supports the following approach. Configure Visual Studio to use use Microsoft IIS Express instead of the web server built in to Visual Studio.