Hi,

I have resolved the issues i have listed on previous posts. Now i have another problem. I got stuck on the login page. The symptoms:

When i run the app, i get the DesktopDefault.aspx page and the login screen. When i enter user/pass it only refreshes the login page, gives no exception and don't let me go further.

i tried to debug the app. I have found out that Context.User.Identity.AuthenticationType value is blank. I think it should have been "Forms".

My web.config file has the following lines;

<authentication mode="Forms">
            <forms loginUrl="DesktopDefault.aspx" timeout="600"/>
</authentication>

By the way i'm using SQL connection and i have the following related lines in the web.config file;

   <add key="ConnectionString" value="Server="Server_name";UID="username";PWD="password";database=IssueTracker"/>
   <add key="DataAccessType" value="ASPNET.StarterKit.IssueTracker.DataAccessLayer.SQLDataAccessLayer"/>
   <add key="UserAccountSource" value="None"/> ... 

I really stuck on this position and need help.

ps: One more debug issue, I put a breakpoint in Login method of the DesktopDefault.aspx.cs file (on the first if clause which is if (Page.IsValid) { ). When i click on Sign-in button, the code never reaches to this breakpoint. I don't know why!

I'm still at the same position. I debug a lot and realized that my app never tries to establish a connection with the DB server. (DB server, IIS and the app all are running on my local m/c). I suspect about the connection string first but whatever i put in the string doesn't matter. I stopped the DB services, same behavior. (When i click sign-in or register with some dummy values in username and password boxes, the app just refreshes the same page, do nothing else, no exception)

 

For the connection string, i have added some lines to web.config such as;

 

  <connectionStrings>
    <add name="ConnectionString" connectionString="Data Source=.\SQLEXPRESS; Initial Catalog=IssueTracker; User ID=USERID; password=PASSWORD;trusted_connection=false" providerName="System.Data.SqlClient" />
  </connectionStrings>

   and

 <appSettings>

    <add key="ConnectionString" value="Data Source=SIM-CUNVER\SQLEXPRESS,56758;Initial Catalog=IssueTracker;User ID=UID;password=PASSWORD"/>
    ...

I think there are some format changes between .net1.1 and .net2.0, that's why i exchange "Server" with "Data Source" and "database" with "Initial Catalog" etc. there are also two connection strings defined in the web.config file. I have tried all the possibilities, defining each of them separately or both of them at the same time (both the "key" and the "name"), but no luck.

I have no clues left, nothing left to try. I think i'm giving up with the issuetracker.

Thanks  

I'm still at the same position. I debug a lot and realized that my app never tries to establish a connection with the DB server. (DB server, IIS and the app all are running on my local m/c). I suspect about the connection string first but whatever i put in the string doesn't matter. I stopped the DB services, same behavior. (When i click sign-in or register with some dummy values in username and password boxes, the app just refreshes the same page, do nothing else, no exception)

 

For the connection string, i have added some lines to web.config such as;

 

  <connectionStrings>
    <add name="ConnectionString" connectionString="Data Source=.\SQLEXPRESS; Initial Catalog=IssueTracker; User ID=USERID; password=PASSWORD;trusted_connection=false" providerName="System.Data.SqlClient" />
  </connectionStrings>

   and

 <appSettings>

    <add key="ConnectionString" value="Data Source=SIM-CUNVER\SQLEXPRESS,56758;Initial Catalog=IssueTracker;User ID=UID;password=PASSWORD"/>
    ...

I think there are some format changes between .net1.1 and .net2.0, that's why i exchange "Server" with "Data Source" and "database" with "Initial Catalog" etc. there are also two connection strings defined in the web.config file. I have tried all the possibilities, defining each of them separately or both of them at the same time (both the "key" and the "name"), but no luck.

I have no clues left, nothing left to try. I think i'm giving up with the issuetracker.

Thanks  

 Hi,

I started all over again and setup the IssueTracker again. This time it worked, but i think i have already solved a lot of authentication and integration problems. That helped me a lot in this new setup

Let me summarize what i did;

In the previous setup, i chose an existing database, now i chose a fresh new one. I also gave-up SQL authentication and now i'm using Windows authentication. I faced a couple of minor problems but i solved them in an hour, so thats it ... A working Issuetracker. Now i can play with it