Re: Problems deploying website with membership features from XP to 2003 (take2)

I believe you can specify 'ApplicationName' in web.config in the Providers
<add> element. Did you try that?

HTH,

Howard Hoffman

"Sam Samson" <nospamsam@xxxxxxxxxxxxx> wrote in message
news:ece03a78e8af8c9d97f8b62bee6@xxxxxxxxxxxxxxxxxxxxx
greetings all, (again blasted newsreader killed my initial epic, email
post numero 2)

I have a dev box(XP) that I am developing an ASP.NET 2.0 application .. am
trying to use membership features .. have set up my local box secured a
directory dropped in an ASP:LOGIN web control added some users set all the
right properties and I have a nicely login secured web app that runs just
dandy on my dev box.

However when I try to deploy to my 2003 server all looks fine but I cannot
log in "Your login attempt was not successful. Please try again."

A blog search has people talking about naming the application .. so using
the IIS management snap-in I have given my web site an application name
("grizzly").. the blogs say this should be reflected in the ASPNETDB,
aspnet_applications, applicationName .. however this applicationName
remains "/" instead of "grizzly" which is what I named the web
application. And to make things even more confusing some blogs say this is
the desirable behaviour.

I am now lost as what to do next. I tried to add users and set security on
my directory on the 2003 machine but can't find an equivalent tool like
the one under VS2005 website asp.net configuration .. and dont know if
this is even the way to do it.

The 2003 server windows event logs are full of "Membership credential
failures" but the fact that I dont get a screen full of stacktrace makes
me think it can at least see the ASPDBNET database nestled away in the
App_data directory

Now I'm quite stuck and looking for a push in the right direction ... it
certainly looks like I should be able to create my site on my dev box and
simply publish it to the 2003 server

Is there a "complete and utter idiots guide" to setting up this kind of
website publishing

---------------------------------------------
[Sam Samson] - There is no greater folly than fixed price quoting.




.

Relevant Pages

  • Problems deploying website with membership features from XP to 2003 (take2)
    ... I have a dev boxthat I am developing an ASP.NET 2.0 application .. ... However when I try to deploy to my 2003 server all looks fine but I cannot log in "Your login attempt was not successful. ... And to make things even more confusing some blogs say this is the desirable behaviour. ... The 2003 server windows event logs are full of "Membership credential failures" but the fact that I dont get a screen full of stacktrace makes me think it can at least see the ASPDBNET database nestled away in the App_data directory ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: What is your database application development environment?
    ... development, then switch to the Test or QA database for optimization, ... both our Dev and QA processes used smaller databases. ... have DEV boxes or CPU cycles that closely resemble QA and production. ... each running SQL Server Developer. ...
    (borland.public.delphi.non-technical)
  • RE: Build Solution from network share in VS2005 wont work - please he
    ... So the problem seems due to the file share communication between your WIN ... 2003 server and WIN XP work station (dev box). ... Build Solution from network share in VS2005 won't work - please ...
    (microsoft.public.dotnet.framework.aspnet)
  • Link servers through proxy
    ... My main development computer, XP Pro, has 2 Ethernet ... Management Studio to access several database on the SQLREMOTE server ... I can see the databases on the SQLTEST computer ...
    (microsoft.public.sqlserver.connect)
  • Re: Quick and dirty system recovery: Is this method OKAY ?
    ... those server do not have dual redundant power supplies. ... "D> do have hardware mirrored disks. ... "D> Shut down the dev server, take both the production disks and put them in the ... and it might not trust the config on the disks themselves. ...
    (comp.os.linux.misc)