Hi guys

I’m new to this forum and I hope you could answer some questions and/or give me some advice.

Since I use VS2010 I wanted to test the newly added functionality of 1-click-package-deploying. It turned out that this functionality isn‘t available for our DNN web page project since it was added as ‘existing website’ to my solution. To get this option showing up the project needs to be created from a Visual Studio web project template. “It can’t be that hard!” I thought and added a new ASP project to the solution. After copying all files/binaries and adding all references as it was in the “old” project I still got five errors from the compiler. I am using DNN 06.00.01 and .NET 3.5

Here an example:
The type 'DotNetNuke.Modules.Admin.Authentication.Login' already contains a definition for 'UseCaptcha' C:\Projects\...\DesktopModules\AuthenticationServices\DNN\Login.ascx.cs

Actually after searching the project I found the definition ‘UseCaptcha’ in two files:
...\DesktopModules\AuthenticationServices\DNN\Login.ascx.cs
...\DesktopModules\Admin\Authentication\Login.ascx.cs

Both files are using the same namespace: 'DotNetNuke.Modules.Admin.Authentication'. As I comprehend OOP it’s completely ok that the compiler throws errors in such situations. And I don’t want to change these settings.

Another example:
Partial declarations of 'DotNetNuke.Modules.Admin.Users.ViewProfile' must not specify different base classes C:\Projects\...\admin\Users\ViewProfile.ascx.cs

Found in the following two files:
...\admin\Users\ViewProfile.ascx.cs(38):     public partial class ViewProfile : UserModuleBase
...\DesktopModules\Admin\ViewProfile\ViewProfile.ascx.cs(51): public partial class ViewProfile : ProfileModuleUserControlBase
Originally they were both derived from the class ‘UserControl’ but again it’s ok when this results in an error.

I have three further errors of the same type:
Partial declarations of 'DotNetNuke.Modules.Admin.Authentication.Login' must not specify different base classes C:\Projects\...\DesktopModules\Admin\Authentication\Login.ascx.cs
Type 'DotNetNuke.Modules.Admin.Authentication.Login' already defines a member called 'OnLoad' with the same parameter types C:\Projects\...\DesktopModules\AuthenticationServices\DNN\Login.ascx.cs
Type 'DotNetNuke.Modules.Admin.Users.ViewProfile' already defines a member called 'OnLoad' with the same parameter types C:\Projects\...\DesktopModules\Admin\ViewProfile\ViewProfile.ascx.cs

Are these errors in the DNN framework or is this intentional?

Why didn’t I get these errors in the other project, are the compiler’s settings less restrictive? Or are there settings on project or files that can be set to prevent compiler errors and successfully build my project? (I had to change the ‘build action’ property to ‘compile’ in order to eliminate some errors in App_Code files)

Are these known bugs and getting fixed (or already are) in a future release so I can use it as I wanted or should I solve the issues by commenting some parts out (then I suspect problems with upgrade compatibility) or is there another simple way to achieve my goal: building a deployment package? What do you suggest, how should I proceed?

thanks in anticipation
snevera

Hi westa

I use DNN as part of my webshop solution (with lots of own user controls) and other projects containing basic functionality. It's this whole solution I want to build a deployment package from, including DNN. So you can import the zip file into IIS and voilà have a working webshop.

how exactly do you mean that?

Apart from all that what's about the issues of duplicate definitions in the same namespace and derivation of partial classes from different parental classes? Is this a valid practice? Not in my opinion...

nevera