chapter 5
  AccountsBusiness

vb: siteprincipal
c#: PhilePrincipal

I want to know which is better,why?And is there any other difference between vb and c#.

Thanks!

The VB version is a little newer. It has some bug fixes, and some small design improvements. Read the .doc file that comes in the VB code download for details.

In this case, there really is no PhilePrincipal class. That was based on an early code draft. The C# code download (and the VB download) only has a SitePrincipal. Wherever you see PhilePrincipal in the book, change it to SitePrincipal.

Eric

Thanks!

1.Can I get the C# code of new version as VB?

2.When I build the project of C#,there are some errors£¬just like:
C:\wrox\ThePhile\Modules\Accounts\ACCOUNTSBUSINESS \AccountsTool.cs(9): namespace¡°Business¡±does exist in¡°Wrox.WebModules¡±
How can i do?

Can I get the whole class tree of it.

1. The VB version is newer, but both of the code downloads are for VS 2002. You can download the code for either version from the Wrox website. Find the book, and then you'll see the links to download the code.

2. It sounds like you have a bad reference. Did you port the code to VS 2003? Both code downloads are set up for VS 2002 and you have to convert the projects and set new references to make them work in 2003.

There is no official source code for use directly in VS 2003. I was hoping Wrox would consider updating the code again, but I don't think they will.

I'd really like to see a revised edition of the book, and that could include code for the new VS 2005, which is already out in beta. There's a number of changes to the design that I've recommended, and it'd be great if we could get all this into a revised book.

Eric

Thanks for your detailedly answer!

Yes,I port the code to VS2003 :)
Then,how can i set new references for VS2003?

Yes,I know it now,thanks again!

Actually how DO i set references for VS2003? I've converted it to 2003, but wasn't aware of any 'references' i need to change...

Any ideas?

J

If it builds cleanly in 2003 then you already have the references. Aren't you familiar with the references under the Solution Explorer? This is where you specify with assemblies you want to use in the current project. Look at the references for your main project and you'll see that shows the other assemblies that are used.

Eric