Hello,
We are using CSLA 3.5.0.0 in our application and trying to run it using ASP.NET Web Development Server. Desktop does not have admin rights so we can't use it in IIS. We are getting error in the class where we are referencing Csla.Security.BusinessPrincipalBase. I read it on book
(http://books.google.com/books?id=9Mbx3Svoc1EC&pg=PA705&lpg=PA705&dq=csla+custom+security+object+limitation+with+asp.net+web+development+server&source=bl&ots=do6mTT2Zzv&sig=aKjqa2a7yi4KoAm4RR741c5o1i4&hl=en&ei=nTI8TKCEDIGdlgf4soj9BQ&sa=X&oi=book_result&ct=result&resnum=4&ved=0CCAQ6AEwAw#v=onepage&q&f=false)
that some components of CSLA can not be used with ASP.NET Web Development Server. I wanted to confirm whether Csla.Security.BusinessPrincipalBase can be used on ASP.NET Web Development Server?
No, absolutely not. BusinessPrincipalBase is not part of .NET, so it us a custom principal, and the dev server can't handle it (easily).
Only GenericPrincipal and WindowsPrincipal will work, and CSLA 3.5 doesn't support GenericPrincipal.
This is one reason Microsoft has (finally) abandoned the dev server in favor of a new dev server that is compatible with IIS7 (see Scott Guthrie's recent blog posts on the topic).
Can this be used when application is hosted on IIS with virtual directory or we need to create Web Site only to run our application. Please note we are using IIS 5.1.
I'm not sure what you mean by "this".
Cassini (the ASP.NET Dev Web Server) doesn't behave exactly like any version of IIS, and one of its quirks is that it doesn't work to run apps that use a custom principal. This isn't a CSLA issue, it is a broad issue with that web server.
So if you have a custom principal in your app, you need to host in IIS to do your development and testing. Any version of IIS that works with .NET should work fine.
It might be the case that this new dev server tool will allow you to do your development and testing without IIS. I don't know, as I haven't had time to try it out yet.
Copyright (c) Marimer LLC