By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
449,438 Members | 1,610 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 449,438 IT Pros & Developers. It's quick & easy.

Weird Compilation Error Migrating from Dreamweaver to VS

P: n/a

hi all

I changed the name of the class LoginPage to a different
name "LoginPageOne" But the same error gets generated with
the Wiliam.Request.LoginPageOne. That pretty much leaves
me clueless at this point.

Please help


Apparently, you have a class which has multiple
definitions within the same
namespace in your code. Should be pretty easy to track
down. Are you using
C#? If so, it is certainly possible to create 2 class
files, define the same
namespace in each, and create a duplicate class within
the same namespace.


Kevin Spencer
Microsoft MVP
..Net Developer
The more I learn, the less I know.

"James Zhuo" <na**************> wrote in
Hi all

I've been getting the following compilation error. I should explain the background of the project that i am taking over. This is a project that
has been developed by someone else a while ago using dreamweaver, I am
basically trying to migrate the project into a Visual Studio .NET environment before
I start enhancing it.

Any suggestions on where the source of error may be would be greatly appreciated.


Compilation Error
Description: An error occurred during the compilation of a resource
required to service this request. Please review the following specific error
details and modify your source code appropriately.

Compiler Error Message: CS1595: 'Wiliam.Request.LoginPage' is defined in multiple places; using definition from
'C:\WINNT\Microsoft.NET\Framework\v1.0.3705\Tempor ary ASP.NET Files\ticketing\51e97ea9\cbdc4eb9\assembly\dl\b46c 1607
\c1f6bd86_7f68c301\Tic keting.DLL'
More details here

Nov 17 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.