Re: VS2005 Compilation message

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Hi Fred,

Indeed the solution in question is a mish-mash of 1.1 web app code. 

OK, that explains a lot!

I just think that V Studio should not flag errors in temp files it itself created.

I think you'll find VS2005 can throw some extremely misleading and confusing errors, but in 9 out of 10 cases you only get this when converting projects from v1.1 to v2.0

The problem is that the converter in VS2005 is crude and the web version has bugs (even after applying the patch). It converts form v1.1 to v2.0 in the same way you could convert Access 2.0 VBA code to Access 95 code using the "wizard". It kind of works but what you end up with in not the same as if you'd coded from scratch to the new methodologies; it's the same with .NET 1.1 to .NET 2.0

We've converted three fairly complex projects this week not only the ..NET stuff but also converting the ASPX pages to XHTML. Once you've done the first one it gets much easier because the errors will be very similar. A brief outline of what we did

1. Get rid of Microsoft Enterprise Library and it's DLLs
2. Use "Web Folders" within Windoze Explorer to "Copy" the whole web project from the FrontPage extended remote production server to a local FileSystem location on the developer machine (e.g. .\Visual Studio 2005\WebSites\myWebProject). Using "Web Folders" will ensure you don't get all the _vti_xxx stuff.
3. Create a new blank solution in your home directory (e.g. .\Visual Studio 2005\Projects\myWebProject\myWebProject.sln)
4. Open the "existing" WebSite from the FileSystem location in step 2.
5. Let the conversion wizard run, but don't make a backup.
6. Note all errors from the conversion log
7. Close the solution, it will probably be broken anyway
8. Delete the *.csproj file or similar from the FileSytem location above, also delete any project DLLs from the /bin folder
9. Re-open the solution; it should open properly now
10. Build the WebSite, and fix all errors and warnings
11. Highlight the WebSite in solution explorer and either choose "View in Browser" or "Start Debugging"; this should run the WebSite from the VS2005 built-in web server and/or test the debugger is working
12. When your WebSite is perfect and better than everyone else's, you are ready to upload it to the production server.

The reason being that there are loads of errors since I'm only trying a concept it makes it difficult to find the real errors. I have to scroll down and work out which I should fix first.

Yes, I tend to start with the first one, and then the next and so on. I think you can "build" one page at a time instead of the whole WebSite, this could be useful for the problem you are describing. It will show you errors for that page only. Note that "build" does not really "build" when you use it for WebSites in VS2005, it just checks the files for errors.

Since I did not write the original project i'm sor of guessing. 

Yes, it's harder when you didn't write the original.

Any hint to make compiling quiker would be nice too. I find the compilation process so much slower than 1.0 or 1.1, and thethe current poject only has about 3 web pages.

VS2005 is slower than VS2003; it's due to inefficient coding behind the scenes. Vista will probably be slower than XP for the same reason.

I recommend you ditch proprietary VB and write the project from scratch in .NET 2.0 using C#, or if you want it to really fly (and be 100 times easier to maintain), ditch Windows and .NET all together and create it on Linux/Apache.

--
Gerry Hickman (London UK)
.

Relevant Pages

  • Re: Fuzzy blured gif text when outposting from Publisher to html
    ... Why are you converting text to an image? ... I am running Microsoft Publisher 2002 to build a simple 15 page website. ... During that time no changes has been made to the system other than Microsoft Updates, ... For example the text boxes with shaded backgrounds “layers” that get converted to gif images during html outpost are very difficult to read. ...
    (microsoft.public.publisher.webdesign)
  • Re: BaseClasses still missing
    ... I downloaded the project file from your website and ... after converting it to VS 2005 and locating ddraw.h on my HD I could build ...
    (microsoft.public.win32.programmer.directx.audio)
  • Re: converting to NTFS
    ... > I want to set up a website in and use Outlook and database ... > WindowsXP encourages converting to NTFS. ... you can still use floppies if you convert to NTFS. ... If you are one of them, complain to my Administrator! ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Recording demo to video
    ... If you donate an amount to the website, they will give you a coupon code, so ... you can get the winner software cheaper. ... of training to encode - next step is converting to actual DVD video ...
    (borland.public.delphi.thirdpartytools.general)