| 3:04 pm on Sep 26, 2006 (gmt 0)|
google "custom membership provider"
| 3:30 pm on Sep 26, 2006 (gmt 0)|
thanks Easy_Coder, printed the first article, it seems we have to upgrade to .Net 2. perhaps i should ask this in another thread, would the upgrade from 1.1 to 2, be fairly smooth in the ealry stages of a project (3 months worth work)?
| 5:10 pm on Sep 26, 2006 (gmt 0)|
I don't know that I could easily say yes. Every application is going to be different. I would recommend trying it with a COPY of your 1.1 application. Don't gank your existing stuff in case it turns out to be a total goof.
I've done a half dozen conversions or more from 1.1 to 2.0 and they weren't straight forward and I wound up re-writing some small chunks. Especially, the code behind. In instances where the code behind didn't work I had to drop and recreate the page then re-stitch the code behind.
I'll tell you what though... .net 2.0 is flippin sweet! Once you get there you will never want to go back into 1.1 or asp code again.
| 5:15 pm on Sep 26, 2006 (gmt 0)|
Oh and I forgot to mention that you'll need vs.net 2005 too.
| 11:23 pm on Sep 26, 2006 (gmt 0)|
Well, you dont *need* vs.net2005.. you can use the Express edition (free).. Dont get me wrong, I use vs2005 myself (and love it) but there are definitely cheaper/free alternatives.
Regarding 1.1 --> 2.0 I havent experienced any issues. Infact, I recently migrated over 3 large'ish applications from 1.1 to 2.0 without any issues at all. There were some warnings here and there about deprected object use (namely ConfigurationSettings.AppSettings to ConfigurationManager.AppSettings and System.Web.Mail to System.Net.Mail) but everything still worked.
Now, regarding 2.0's membership mangement. I *hate* the drag/drop crap that they tried to implement.. yeah, its nice for trivial concept sites or whatever, but it sucks for anything significant IMHO. Thank God they allow us to make our own providers, thats really the nice thing about .NET 2.0 I guess..
| 2:34 am on Sep 27, 2006 (gmt 0)|
man I have been missing out! I read about the >net 2 membership classes, its cool, compared to what we did in mono.
i have got VS 2005, have been sorta hesitant to install it. i think i just go ahead and have 2003 and 2005 run side by side! now i am intrested to know more about this .Net 2 :-)
PS: i dont like drag and drop either.
| 10:51 am on Sep 27, 2006 (gmt 0)|
You shouldn't have a problem running vs.net 2003 and 2005 side by side. I've got it set up that way on 2 machines with sql server 2005 and 2005 running side by side too.
I've not been a huge fan of drag n drop stuff but I have to admit that some of the features of the gridview are really nice. Like inline editing... I don't have to wire it up myself.
| 6:10 pm on Sep 29, 2006 (gmt 0)|
hhhm, okay i am migrating ... well build not successful yet, it 'can not load type someClassName' error
why the *.resx files are not nested?!
| 7:24 pm on Sep 29, 2006 (gmt 0)|
I ran into the same issue with the resource files and when that happenned I had to reintroduce those pages (save code, delete page, create new page and stich code back in).
See if you can make a change to your code behind and them re-compile. BTW, when you save now you'll notice your changes going right out. That's a nice feature... but for this .resx issue try to do a rebuild.
| 7:57 pm on Sep 29, 2006 (gmt 0)|
thanks easy_coder. re-build didn fix it.
I added a new page [test2.aspx](in VS 2005) and it didn have .resx automatically ...hhm
yea i noticed the absence of the good old bin/dlls. hhm i am lil bit nostaligic already; however teh new on-the-fly dll creation seems quite fast! (i managed to have a successful build)
| 3:46 am on Sep 30, 2006 (gmt 0)|
Yeah, 2.0 is sooooo much faster. Glad to hear you got it working.