Hello, Goran.
Current version of the Cassini web server does not support Windows authentication, but the
upcoming new one will. For now your application will not get client user's identity if served by Cassini running as a service. Forms authentication would be the only possibility for now. As for how to store user-specific, you may certainly store data in user-specific profile folders, but if a remote user accessed your application, the server may not even have the profile folders created for the user, and creating a profile on the machine could be pretty time-consuming and taking up quite a bit of disk space.
If you don't plan to provide remote access to the application, then you probably want to run Cassini as an interactive EXE, in which case Cassini will run as currently logged-in user instead of as a service and it will have complete access to all user's folders. In this case the identity of user will be determined no by the user identity of the browser, but the user identity of the server.
Exe to run is:
"C:\Program Files (x86)\UltiDev\Cassini Web Server for ASP.NET 2.0\UltiDevCassinWebServer2.exe"
Code:Usage:
UltiDevCassinWebServer2.exe /run <PhysicalAppFolder> [<defaultDocument>] [<port> | 0] [<browser path> | nobrowser]
UltiDevCassinWebServer2.exe /register <PhysicalAppFolder> [<AppGUID>] [<defaultDocument>] [<port> | 0] [/DontKeepRunning]
UltiDevCassinWebServer2.exe /unregister <AppGUID>
Commands:
/run - launches stand-alone (unregistered) ASP.NET application under Cassini server.
/register - registers an ASP.NET application with Cassini.
/unregister - unregisters an ASP.NET application from Cassini.
You will probably have to use "nobrowser" option because browsers nowadays merge processes when there is another instance of the browser, making Cassini think the browser failed to start.
Best regards,
UltiDev Team.
Please donate at
http://www.ultidev.com/products/Donate.aspx to help us improve our products.
