cassini

We are trying to get our .NET devs to use the ASP.NET Development Server (VS2008) for web development instead of a local instance of IIS . I received this response as a reason why some of our devs can't use it: "Our XXXX Online Sales application uses SSL to protect passwords. While Visual Studio does permit some basic web application development without IIS, the light weight replacement does not support SSL." Does this make sense? Is there a work-around? Thanks! The web server built into VS doesn't not support SSL. It is meant to be a quick way to test an application. For SSL, you would need

I'm developing an application that is so far using HttpListener to provide a small standalone http server. However, I've recently discovered that HttpListener needs to be run as Administrator, which is not always going to be possible. What would the best alternative be? I need http GET and POST, both of which are not simply reading/writing files on the filesystem, they need to run custom .Net code. My research so far has brought up Cassini, but as far as I can tell, I would have to write a custom version. Is there anything else? In partiular something with the same interface as HttpListener,

I can't seem to find any information on this anywhere. Either it's my imagination or the ASP.NET Dev Server (Cassini) cannot handle multiple threads (e.g. multiple requests). Is this correct? Does IIS Express handle multiple threads? Yes, functionally speaking, cassini processes one request at a time. IIS Express is an almost full IIS implementation and will provide expected performance. 来源： https://stackoverflow.com/questions/3261144/asp-net-dev-server-cassini-iis-express-and-multiple-threads

Visual Studio is asking to create virtual directories in IIS when I open a solution. Could this be because projects within the solution have been configured to use IIS rather than Cassini? The dialog message is: "The local URI ... specified for Web project ... has not been configured. In order to open this project the virtual directory needs to be configured. Would you like to create the virtual directory now?" Yes it is. If a web project is configured to use IIS (on the Web tab in the project properties -> "Use local IIS web server"), Visual Studio requires that the path defined exists in IIS

I've recently returned to a web site project that has been on the backburner. Since recommencing work I've noticed css and javascript changes aren't being recognised by the application when it's running in Visual Studio Development Server. This previously worked fine. I could change stylesheets and javascript and run the app and test. Now the only way I can test the application is to publish it to my local IIS server (though I believe restarting my pc also fixes the problem). Using Visual Studio 2008 (9.0.30729.1) The things that have changed since I am certain it was working correctly is the

I'm now developing on Visual Studio 2008 on a 64-bit OS (Windows Server 2008 64-bit). While the apps I write are 64-bit capable, as is IIS7, the built-in ASP.NET Development Server (aka Cassini aka WebDev.Webserver.exe) runs as 32-bit. This brings up a plethora of issues, such as: 32-bit and 64-bit applications have separate HKLM\Software registry homes There are 32-bit and 64-bit versions of the SQL Server Client Network Utility Other fun surprises I haven't discovered but I'm sure will spring up While I am finding workarounds for most of this, I have to ask... Does anyone who has played with

Currently our dev team set up all the websites they're working on in IIS on their local machine. We're thinking of switching to using the built in ASP.NET development server instead. Is this a good idea? What are the pros / cons of using the ASP.NET dev Server? Are there any gotchas we should be aware of? Thanks. NB: Running on Win XP / IIS 5 / VS2005 Edit: Didn't realise it was called Cassini.. More answers for Cassini v IIS here . There is nothing that the ASP.NET Dev WebService can do that IIS can't (You can set breakpoints etc, just attach the VS debugger to the ASP.NET runtime). However,

Is there a way to automatically stop the ASP.NET Development Server (Cassini) whenever I do a build/rebuild in VS2008 (and then obviously have it start again when required)? Maybe there's some hidden configuration setting somewhere? Or at least some way to do it as a post-build event maybe? For some background, the issue is that I'm using Spring.NET for dependency injection, etc, but it loads its singletons on Application Start, meaning that if I change any spring related code/configuration I have to stop the Development Server, so that it starts again next debug/run ensuring the Application