#
#
#
#
#
#
#
#
#
#

As I said in another msg a few minutes ago, you need to properly upgrade the solution to .NET 1.1. You have references in there for .NET 1.0.

This is a big job if you're not very familiar with ASP.NET because you have to delete your DLLs and re-create them. It sounds easy, but it's a couple hours of work.

>Is it the first type of warnings that should be corrected
>in the way you describe?
>WARNING: Unable to find dependency 'MSCORLIB'
>(Signature='B77A5C561934E089' Version='1.0.3300.0') of
> assembly 'Wrox.WebModules.Accounts.Configuration.dll'

This is the version number for .NET 1.0, so you are referencing a DLL that was compiled with 1.0.

It's difficult to explain how all this works in a message, but the general idea is that a Visual Studio reference is tied to a particular DLL. If it references a DLL made under an old version of .NET, it might work in some cases, but should never be done that way because its too risky. You need to delete the DLLs and PDBs (the PDBs are only used for debugging, but you don't want old ones), which then breaks your references in VS. You'll see an error indicator if you drill down on the references in the Solution Explorer.

To fix the references you need to delete them, and set a new reference to a DLL created with the new version of .NET. This becomes a "chicken and egg" question: how can you reference a DLL that doesn't exist? The bottom line is to work out the dependencies. At some point you can compile at least one of the projects within the solution, and that DLL can then be referenced by other projects. You slowly go thru the projects this way - trying to build all you can, and then fixing the references for the other projects that refer to the DLL(s) you just built.

Warning: when you see a broken references in the solution explorer, do NOT delete them all. I first make sure that I have a new DLL for that reference before I delete it, then I delete it and set the new reference. If you delete more than one at a time you might get confused about which new references you need to make.

The easy way is to keep doing a Rebuild of the whole solution, pay attention to what built OK, then go fix any other project that refers to the DLL(s) that built OK.

I'll see if I can post my C# project for people to download. My biggest problem is that it's quite large and I don't want to pay a lot of money for the bandwidth on my web site to have people download the file. If anyone can host this ZIP file for me on a public website, please let me know.

Eric

I've coordinated with user "ms" to post my copy of ThePhileII on his server. Anyone who's having trouble getting the basic site working may want to download this and check it out!

Here's some items that you need to know:

- this code is only for the C# version
- it has a lot of security-related bug fixes
- it has been updated to use Visual Studio 2003 and ASP.NET 1.1
- it logs errors to a file and does not use the EventLog
- it has been changed to run as the virtual root, which is needed if you'll deploy to an inexpensive hosted website
- it has it's own database creation procedures that use only SQL files
- you can setup the database using the free MSDE or a full version of SQL Server 2000
- it has a summary of changes and detailed step-by-step setup instructions
- I assume you are generally familiar with IIS, ASP.NET, and SQL Server. The instructions will NOT teach you these basic items.

Of course, these files are given out "as is". It's your responsibility to properly use the files and change them to meet your needs. Further, only owners of the book "ASP.NET Website Programming" are legally entitled to use these files.

I do not work for Wiley/Wrox Press as a support person, and I can only offer a limited amount of support. You should not count on me being able to fix all your problems [:-)]

You can download the project here:

http://design-programmering.net/down...thephileII.zip

Good Luck - this should get you going! Or, if you're already going, you should probably check into the security fixes given here. I've mentioned the security issues here before, and I don't want to keep hitting on this, but I consider the security holes in the original project to be serious and fixing the holes should be everyone's first order-of-business.

I have not done a complete review of the VB.NET version, but I've noticed that it fixed some of the bugs, but not all of them. I simply don't have enough time to back-port my changes to the VB.NET code at this time. Please check ThePhileII-changes.txt to see if you may need to make some of the changes to the VB.NET code.

By the way, this is not my absolute newest version. I changed a lot of foldernames and reorganized files in the version I have at my website, so this won't be an axact match of my website. I don't want to get too far from the book in the files I give out, so I think you'll find this to be a happy medium.

Eric

Eric, thank you for saving me hours and hours of work, people like you should be appreciated.

Thanks for you help hosting this file, Morten. I'm sure people will be able to find it. The interest in this first edition has gone down a lot in recent months but there are still some people reading the first edition.

Eric