ng an application that listens on port 25. My application will work as a SMTP server receiving emails. I am aware that I can just enable IIS SMTP feature, but for my current project, I needed to do in this way.If I can send emails to visual studio development server which has a private IP, my debugging will be much easier. Is there a way to send emails to VS development server?
i have an aspx page, that takes in user data (name, number & email) after that information gets submitted to me, I need to send an email to their input email, with a message of confirmation.
I'm a .NET specialist working with a PHP/Flash programmer to deliver an app via IIS. After jumping through 17 hoops of fire and defeating a gargoyle in a gruesome battle to the death, I managed to get my IIS 7.5 server to cooperate with PHP, and now if you browse to my public web site, you can see the Flash objects happily doing their behind-the-scenes stuff with PHP, whatever that may be.
But... when I'm debugging my app using the VS Development Server, that still apparently doesn't know how to cope with PHP: I'm getting the same HTTP 405 (Method Not Allowed) errors that I was getting on IIS before aforementioned gargoyle breathed its last ("The HTTP verb POST used to access path '/php/blah.php' is not allowed.").
So, what do you have to do to get the VS Dev Server to play nice with PHP?
When debugging my website project I usually go to start options in the web project's properties and select 'Don't open a page' and 'Use custom server' with a url that's in my host file pointing to my local IIS.
Even when I do this though visual studio still spawns it's own Development Server instance every time I hit f5.
Also for web application projects that have shared ascx files for instance Visual Studio will also launch an instance of Development Server each time I debug the solutions for each for these projects. This results in a million instances of Development Server running on my machine at any given moment.
Is there any way to disable development server for a given project completely? Without pointing it to a localhost sub application?
I'm getting "Cannot connect to ASP.NET development server" almost every time I stop the ASP.NET server before restarting the project in debug mode. It can take between 15 seconds and 2 minutes to get the error message, and Visual Studio is frozen.
Sometimes I get three in a row, and I have to wait 2 minutes each time, or go into Task Manager and kill to process. Then I have to start Visual Studio 2010 again, which is at least three times slower than Visual Studio 2008 to open.
It's *extremely* annoying. I know I don't have to close the server if the code has changed, but sometimes I simply want to restart my website in debug mode (there is a cache on most web service calls, so this clears the cache). A workaround is to add "foo" code to a class and restart the project.
I'm running Visual Studio 2010 Professional on Windows Server 2008. I'm running the Visual Studio Power Tools too, with the latest update.
Under IIS I would have to do a special configuration to support PHP. I have also found a number of references related to previous versions of VS which state that the development server would not, hence my question. Will the development server run the following PHP script server side in the header? Are there special configuration requirements?
A number of developers trying to create Silverlight apps intergrating Facebook have ran into the same wall with the MS Facebook SDK, and are struggling to determine the cause. I am assuming the script file contains the integration functions.
i want to know how do i deploy ASP.NET web applications on client machines which runs with the visual studio development server rather than configure it in the IIS on the client machine? I know its possible and telerik also uses this approach.
I'm getting this problem with one of my web projects. I've looked at [URL] and other suggestions around the place, none of which apply here. The odd thing is, it's occurring with *one* of my new web site projects, but not another one. Odd again is that they're both 100% fresh sites, created with the "New Web Site" option in the File menu, within a day of each other, and nothing has been done to them, apart from a bit of "hello world" html. WebSite1 was created first, and Cassini worked when I first created it the other day. A day later, I created WebSite2 and Cassini worked (and still works) with that one.
However, when I open WebSite1, I get the above error code - again, it was working fine the other day, and WebSite2 works fine. I've compared their .sln file - so differences apart from the VWDPort number used, and of course the path to the site and various GUIDs. Everything else is identical. Same with comparing web.config files. No differences there at all. So I'm stumped - why would Cassini start up fine with WebSite2 (and subsequent sites I create) but suddenly stop working for the WebSite1 project, when it was working ok a couple of days ago?
I'm attempting to run/debug an ASP.NET MVC project under .NET 4.0 using VS2010's Dev Web Server. The server appears to spawn successfully and an instance of IE Explorer opens. However, the browser never seems to find the page. The browser just "spins" showing only a white page...no error message.VS is configured to randomly select a port, although I get the same results when configuring numerous static ports.The ASP.NET project is the start-up project.
When viewing an asp.net page in visual studio 2008, the asp.net development server icon shows up in the system tray. It can be stopped by right clicking on it and select "stop". In Visual Studio 2010, I do not see the icon any more. where the asp.net development server is? How to stop it?
I have a test website with VS 2008 that just uses code behind files, such as Foo.aspx.cs. Thus, the web server compiles them on the fly. The problem I'm running into is I can't use any C# 3.0 features. If I do:
[code]....
Then VS will work fine (everything gets highlighted and Intellisensed), but when I run the site it just throws up compiler errors..
Is there a way to fix this, or do you have to compile a DLL to target the 3.0 runtime? If so that's insanely lame.
Not too long ago I was given a new PC with windows 7 Professional on it. Before, I had vs 2008 running on win xp which worked OK. I started getting error msg (Unable to connect to ASP.NET development server) after I installed vs 2008 (version 9.0.30729.1 sp1 vs team system dev. edition) and ran one of my projects and even a simple test project. The first msg shows the syntax of webdev.webserver with an example in the bottom. I can get this error by running the project or by showing any page in the browser. I noticed that file WebDev.WebServer.EXE does not appear in the folder C:WindowsMicrosoft.NETFrameworkv3.5. If that's the only reason why I am having this problem than how can I fix it. I was told that .net framework 3.5 works on top of .net framework 2.0?! I just want to sort out this .net framework mess on my new machine. I am willing to uninstall all .net framework and start fresh. Another thing that I am willing to try is to get from a coworker the WebDev.WebServer.EXE (from the .net framework 3.5 folder) and see if it works.
I noticed a layout issue on the web app I'm working on, and in trying to correct it via the stylesheet I realized that the development server is not recognizing any changes I make to the .css file. As confirmation, I saved a blank stylesheet (which should have removed all styling), cleared my browser cache and rebooted my development machine and the original styling remained. It seems some version of the stylesheet is "stuck." The stylesheet is referenced in my master page, and the path specified is correct.
Debugging using the ASP.NET Development server is extremely slow to initialize. The behavior I'm getting is that if I launch the DevServer from VS2008, the first attempt to load a page takes minutes. After that, it's fine. Before the first page load, the DevServer UI responds to input normally (I can bring it up from the status area, use its context menu, and move the window around) until the first page load comes in. Then it shows the busy cursor (spinning blue ring) for 2-6 minutes before finally completing. There is no significant processor or I/O activity during this. After that, it runs normal speed, quite fast.
I have VS 2008 with SP1 installed on Win XP. I have .NET 3.5 with SP1 installed When I ran and opened an existing project for the first time, I got the below error WebDev.WebServer.exe has encountered a problem and needs to close. After this error, I continusly get "Unable to connect to the ASP.NET Development Server. whenever I run the website. I checked the internet and ASP.NET forum and tried all the following Making port numbers auto assign Making it to a specific port number using the Custom web server Tried creating new web site and checking Replaced WebDev.WebServer.EXE after downloading it from a website My anti virus have not blocked any websites as such I tried resetting VS settings by running devenv /resetsettings what else might be the problem?
I developed a website project using visual studio 2008 and language used is c#. It was working fine till yesterday[i.e., It compiled and also i could run it using the asp.net development server by pressing ctrl+f5] and today when i tried to run it says "unable to connect to asp.net development server". I tried to reinstall visual studion 2008 and even now its not working. Also when i go to websites n asp.net configuration option it say the same error "unable to connect to asp.net development server". I absolutely no idea about why this error popped up. I got my project demo. day after n how can this be set right.
I got these errors while trying to run a web application using vs 2008, The first error is this: >Application has generated an exception that could not be handled. >process ID=0x1130 (4400), Thread ID=0xe6c (3692). And when I press OK a second dialog reports this error:>unable to connect to the asp.net development server. I reinstalled, repaired and re registered msdbg2.dll and edited hosts file but still get this error. I need to debug an application but I can't. This error is on a 'Win 2003 server enrterprise service pack 1' with a vs2008 team system installation. What can I do to remove this error and run and debug my application?
I wrote a web service to send emails and some win apps supossed to call the service for sending emails. When I test the service via Visual studio development server everything is ok and it sends emails. But with IIS the smtpclient.send throw an exception whit this message : No connection could be made because the target machine actively refused it [mailserver ip:port] The endpoint for VS development server is [URL] and for iis [URL] The smtp server is remote (gmail) and iis version is 6. I set the current local user as iis anonymous user. I am in LAN and my client firewall is off. There is an ISA server for the internet but I'm using a dialup connection for the internet. So why visual studio can send emails but iis can't?
I have an ASP.NET site running on the Visual Studio Development Server. I also have a silverlight project in my solution. I get the error:
Error: Unhandled Error in Silverlight Application Code: 2104 Category: InitializeError Message: Could not download the Silverlight application. Check web server settings
After some research, it seems I need to do the equivalent of setting the MIME type in HTTP Headers in IIS for VSDS. Is this right?
If so, how do I do this? If not how do I get my silverlight to run in my ASP.NET solution using Visual Studio Development Server?
I had archived all of my files prior to the change. Since I am now having a great deal of trouble working with 2010, I want to revert. My question is: If I restore all of the archived files and start 2008, will I need to make any changes to the registry or to any other files?
The problems that I am having are illusive. Some of the relative paths nolonger work. Some f the projects that had been working for 24 months no longer functions. I am having a great deal of trouble calling my older "[WebMethod]" "ASMX" services and many other issues.
I just started getting the error message "Unable to Connect to the ASP.net Development Server" when debugging a website with VWD 2008 (everything was fine in the past). My system is Windows Vista with Windows Live OneCare firewall. I have reviewed other postings related to this problem, and they indicate firewall setting problems - settings not allowing VWD internet access. However, my settings on the "Windows Live OneCare Firewall Advanced Settings" tab specifically allow VWD.
I am developing a single web application that will dynamically change its content depending on which domain name is used to reach the site. Multiple domains will point to the same application. I wish to use the following code (or something close) to detect the domain name and perform the customizations:
[code]....
I would like to test the functionality of the above using the ASP.NET development server. I created mappings in the local HOSTS file to map [URL] to 127.0.0.1, and [URL] to 127.0.0.1. I then browse to the application with the browser using [URL] (etc).
When I try to test this code using the ASP.net development server the [URL] always says localhost. It does NOT capture the host entered in the browser, only localhost.
Is there a way to test the URL detection functionality using the development server?
I have a Web App (VS 2010 Beta 2, using VB) and it works flawlessly on the development system. When I publish it, everything works fine unless I use an update panel. If I use the update panel, and try to use something such as a dragpanel, I get the following error.
Webpage error details
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; InfoPath.2; .NET4.0C; .NET4.0E) Timestamp: Thu, 4 Mar 2010 14:54:25 UTC
Message: Sys.WebForms.PageRequestManagerServerErrorException: An unknown error occurred while processing the request on the server. The status code returned from the server was: 404