I am at a point where I would like to upgrade to .Net 2.0, but I don't want to break IssueTracker.  Has anyone has issues with this?  If so what were the issues.  Any info would be great.

Thanks,

Dycacian

Thanks,

I upgraded, and i didn't find any problems.  So at least I know it is still working. 

DarrenC:

Quick question, guys ... If I upgrade to ASP.NET 2.0, will I need to port my database to SQL Server 2005?

Xanderno:

DarrenC:

Quick question, guys ... If I upgrade to ASP.NET 2.0, will I need to port my database to SQL Server 2005?

Nope....No worries there.  SQL Server 2000 (or Access, for that matter) will still work just fine.  

Great... many thanks.

Dycacian:

I am at a point where I would like to upgrade to .Net 2.0, but I don't want to break IssueTracker.  Has anyone has issues with this?  If so what were the issues.  Any info would be great.

Yes. Persisted authentication credentials via encrypted cookies broke after updating the site to run on ASP.NET 2.0. Resolution was to either delete the cookies on the web browser or have an error handling routine to reset the cookies. We chose the latter, but now the cookie doesn't persist longer than 30 min... still looking into it.

Jon

Xiaoth:

Dycacian:

I am at a point where I would like to upgrade to .Net 2.0, but I don't want to break IssueTracker.  Has anyone has issues with this?  If so what were the issues.  Any info would be great.

Yes. Persisted authentication credentials via encrypted cookies broke after updating the site to run on ASP.NET 2.0. Resolution was to either delete the cookies on the web browser or have an error handling routine to reset the cookies. We chose the latter, but now the cookie doesn't persist longer than 30 min... still looking into it.

Jon

To be fair though (and pedantic, while I'm at it :-) ) that's not an issue with Issue Tracker...That's an issue with changing the runtime environment from ASP.Net v1.1 to ASP.Net v2.0.   You'll see this most any time you have an existing ASP.Net 1.1 application using form auth, where you've persisted the forms auth cookies, and you switch it to run under ASP.Net 2.0.  

Not that it's not a valid issue to look out for, but it's an issue to look out for anytime you update an existing 1.x forms auth app to 2.0. 

BTW...Your issue with the cookie not persisting longer than 30 minutes is due to a change in how ASP.Net 2.0 determines the timeout of persistant forms authentication cookies.   You can make them persist longer by increasing the "timeout" attribute of the forms element in the authentication node of web.config.

Hope this helps,

Xander

Xanderno:

Xiaoth:

Yes. Persisted authentication credentials via encrypted cookies broke after updating the site to run on ASP.NET 2.0. Resolution was to either delete the cookies on the web browser or have an error handling routine to reset the cookies. We chose the latter, but now the cookie doesn't persist longer than 30 min... still looking into it.

To be fair though (and pedantic, while I'm at it :-) ) that's not an issue with Issue Tracker...That's an issue with changing the runtime environment from ASP.Net v1.1 to ASP.Net v2.0.   You'll see this most any time you have an existing ASP.Net 1.1 application using form auth, where you've persisted the forms auth cookies, and you switch it to run under ASP.Net 2.0.  

Not that it's not a valid issue to look out for, but it's an issue to look out for anytime you update an existing 1.x forms auth app to 2.0.

Perhaps I consider it an Issue Tracker issue because Issue Tracker persisted the auth cookies in the way that it did. This would not happen if the peristence method used did not use the Crypto libraries that changed between .NET versions; just storing username/password as a cookie using the cookie collection manually does not break, but in this case it did.

Xanderno:

BTW...Your issue with the cookie not persisting longer than 30 minutes is due to a change in how ASP.Net 2.0 determines the timeout of persistant forms authentication cookies.   You can make them persist longer by increasing the "timeout" attribute of the forms element in the authentication node of web.config.

Hope this helps,

Indeed it does, thank you. I wasn't sure what to do about this; thought it was due to a change I made but now I see it's not, and also now know where to go to fix it. Thanks so much.

Jon

Do we have Issue Tracker Starter Kit for .net 2.0.

hello there people, sorry to wake this thread.

the 2.0 project is missing the .sql script files and i can't open the 1.1 tracker on my vista machine, can somebody please email me the database script, i'd like to get this running please...

will have to create a XP VM to run the msi in the mean time...

 thank you.

There is a 2.0 C# version on Codeplex. If anyone has a VB version converted to 2.0 I'd love to get a copy.

 Thanks

Did this project get removed from the asp.net list?  There is a link to axo soft but the starter kit is gone.  Did I miss something? 

I found it in the asp.net 1.x archive.  The axo soft app is totally overkill for what I need.