I've been trying to get the downloaded code to work on a webserver located on our network, not on my local machine. It is company policy not to run webservers on our local machines. I'm also using VS.Net 2003 rather than ver 1.0 and so far I have been unsuccessful (after 1+ week) getting it to work in our environment. The webserver is not on the same domain, so I need to use FPSE to access it rather than file access mode. I am using the C# version of the book/code, so I'm not sure if the instructions that make reference to VB in directory names. etc. is appropriate in this case. Can anyone tell me if it is possible to run this thing on a remote web server, and if so, what modifications do I need to make to the code? When building the solution I get errors like "C:\stuff\VSWebCache\<remote machine name>\ThePhile\AdDetail.aspx.cs(12): The type or namespace name 'AdsManager' does not exist in the class or namespace 'Wrox.WebModules' (are you missing an assembly reference?)", et. al.. Thanks.


Regards,

Jerry

Of course it's possible. My site is remote, and I don't even know what state it's in (I bought an account over the web). I also use Front Page Server Extensions.

I'm using the VB dir names that I got from the doc file in the VB code download because they make more sense, and they line up with namespaces better. But my code is 100% C#: http://www.ericengler.com

Are you deploying to a virtual directory named ThePhile?

It sounds to me like you didn't upgrade the code to VS 2003 correctly.

Eric

<snip>
Are you deploying to a virtual directory named ThePhile?
>>>Yes
It sounds to me like you didn't upgrade the code to VS 2003 correctly.
>>Prolly not. I'm pretty much a newbie w/ C# and .Net, so prehaps you would be kind enough to tell me if there is a wizard or tool that will do this automagically? When I opened the project in VS 2003, it just informed me that it would convert it to the new format and this would not be backwardly compatible w/ v 1.0. Are there code changes you had to make manually?

Thx.

Jerry:)

No code changes are needed, but you have to delete all the .DLLs and .pdb files that were compiled with VS 2002, and that means your references will be lost. You will have to "Rebuild all" in VS 2003, and it will probably stop several times and give errors about missing references. Thats when you have to set the reference with the new 2003 DLL's you made. This has to be done repeatedly until you get a sucessful "Rebuild all" using VS 2003.

This isn't a good project for newbies. You may find it hard to work with until you have more experience.

Eric