Migrating to VS 2005, really too hard!
I am really optimistic by nature (yes it’s true) but the migration to VS 2005 is really too hard :-(
If only my boss could let met six months alone on a (tropical) remote island with my laptop, few .Net 2.0 books (and a good provision of beers) yes I will be so happy.
But in my not so exotic life, I have to deal with many things and I don’t get the thing, too much things going wrong, really hairy and scary.
Now I decided a new approach. I am going to rewrite my project from scratch in VS 2005, copy the stuff I need from VS 2003, lost a lot of sweat on the way, but hopefully I should have something working in the next 20 days.
UPDATE: Yes it works much better and it’s also a great way to discover what’s going wrong. OK it take a lot of more time but you finish with a much cleaner project.
Keith asked me why I have so many problems, so yes OK I will try to share.
– All my projects included in the solution disappeared. OK fine, but if I follow well when I start from scratch in VS 2005, I can have almost exactly the same structure than in VS 2003. So why the migration tool can’t do the same?
– all the .Resx files appears out of their usual place.
VS 2003
Webform.aspx
—> Webform.aspx.vb
——-> Webform.aspx.resx
VS 2005
Webform.aspx
—> Webform.aspx.vb
Webform.aspx.resx (same level than the aspx file)
I have no clue what to do with those files, should I delete them?.
– Show All files doesn’t seems to work in a web project.
This is just the start, the list can really be too long.
Now starting again from scratch and copy and paste my code I have less problems except this one:
If I add a Class Library to an existing web solution, everything fine. But if I reference from the web project the class library I don’t understand why the class library files are duplicated in my web project. Maybe the way I reference the project is wrong??