S
Sean
I am trying to run one SQL Express database for two separate applications
that will also use the Membership framework. My database is set up fine and
works between both applications 100% as needed with the exception of
Membership which I am fairly new to.
From my understanding given the following link
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnpag2/html/PAGHT000022.asp
I need to install membership on the database. So I did the following:
(allow remote connections with TCIP/IP and named pipes)
Started SQL and even re-booted
RUn: aspnet_regsql.exe -E -S localhost -A m
I even tried to run it by replacing localhost with MSSQL$SQLEXPRESS
All attempts gave me an error saying it could not connect and most likely
because remote connections is disabled.
I think the reason for all this is because I don’t actually have the “realâ€
IIS installed but rather I am using the instantiated version that
automatically comes up when starting a ASP.NET 2.0 application.
I am assuming I need to set everything up such that I am using the real IIS
rather then the default one in visual studio.
Is this correct? Or do I have something else?
For those intrested what I am trying to do overall is have a web service
that provides the core application logic and have it feed to both a website
and a desktop application. In addition to using the full membership framework
for the web application.
that will also use the Membership framework. My database is set up fine and
works between both applications 100% as needed with the exception of
Membership which I am fairly new to.
From my understanding given the following link
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnpag2/html/PAGHT000022.asp
I need to install membership on the database. So I did the following:
(allow remote connections with TCIP/IP and named pipes)
Started SQL and even re-booted
RUn: aspnet_regsql.exe -E -S localhost -A m
I even tried to run it by replacing localhost with MSSQL$SQLEXPRESS
All attempts gave me an error saying it could not connect and most likely
because remote connections is disabled.
I think the reason for all this is because I don’t actually have the “realâ€
IIS installed but rather I am using the instantiated version that
automatically comes up when starting a ASP.NET 2.0 application.
I am assuming I need to set everything up such that I am using the real IIS
rather then the default one in visual studio.
Is this correct? Or do I have something else?
For those intrested what I am trying to do overall is have a web service
that provides the core application logic and have it feed to both a website
and a desktop application. In addition to using the full membership framework
for the web application.