VSWD Express & DotNetNuke 4 Code Base Rebuilds - Extend It! ( Programming in VS2005 & 2008, ASP.Net 2.0 )

Forum General DotNetN... Extend It! ( Pr... VSWD Express & DotNetNuke 4 Code Base Rebuilds

2/4/2006 9:41 AM

	Simon Rear
5 posts

VSWD Express & DotNetNuke 4 Code Base Rebuilds

Hi,

I''ve dabbled with DotNetNuke 3.1 using Visual Studio 2003 and am considering moving to v4x but have two quick questions I hope someone here could answer for me....

- Am I correct in assuming I will be unable to modify and recompile the DotNetNuke4 code base with just Visual Web Developer Express?
- In Order to use DotNetNuke4 I must use Visual Studio 2005, (i.e. I can not use Visual Studio 2003)?

Regards,

Simon

2/11/2006 7:53 AM

	Tommi Laukkanen
2 posts

Re: VSWD Express & DotNetNuke 4 Code Base Rebuilds

Hi,

according to the information I have found in the net you should be able to compile at least the website part of the 4.0 distribution especially if you use the starter kit to create the project. For some reason or another I was not able to build the 4.0.2 distribution with neither Visual Studio 2005 Pro nor with Express edition. In both cases I got the following errors:

Error    1    Name 'IsAdminControl' is not declared.    E:\Homes\DotNetNuke_2\Website\admin\Containers\Icon.ascx.vb    93
Error    2    Name 'ProcessModuleLoadException' is not declared.    E:\Homes\DotNetNuke_2\Website\admin\Containers\Icon.ascx.vb    108
Error    3    Name 'ProcessModuleLoadException' is not declared.    E:\Homes\DotNetNuke_2\Website\admin\Containers\LinkActions.ascx.vb    53
Error    4    Type 'UserInfo' is not defined.    E:\Homes\DotNetNuke_2\Website\admin\Containers\LinkActions.ascx.vb    75
Error    5    Name 'PortalSecurity' is not declared.    E:\Homes\DotNetNuke_2\Website\admin\Containers\LinkActions.ascx.vb    76
Error    6    Type 'PortalSettings' is not defined.    E:\Homes\DotNetNuke_2\Website\admin\Containers\LinkActions.ascx.vb    76
Error    7    Name 'IsAdminControl' is not declared.    E:\Homes\DotNetNuke_2\Website\admin\Containers\LinkActions.ascx.vb    77
Error    8    Name 'SecurityAccessLevel' is not declared.    E:\Homes\DotNetNuke_2\Website\admin\Containers\LinkActions.ascx.vb    77
Error    9    Name 'ProcessModuleLoadException' is not declared.    E:\Homes\DotNetNuke_2\Website\admin\Containers\LinkActions.ascx.vb    107
Error    10    Name 'NavigationProvider' is not declared.    E:\Homes\DotNetNuke_2\Website\admin\Containers\SolPartActions.ascx.vb    80
Error    11    Name 'NavigationProvider' is not declared.    E:\Homes\DotNetNuke_2\Website\admin\Containers\SolPartActions.ascx.vb    81
Error    12    Name 'ProcessModuleLoadException' is not declared.    E:\Homes\DotNetNuke_2\Website\admin\Containers\SolPartActions.ascx.vb    111
Error    13    Type 'NavigationProvider.NavigationEventArgs' is not defined.    E:\Homes\DotNetNuke_2\Website\admin\Containers\SolPartActions.ascx.vb    115
Error    14    Name 'ProcessModuleLoadException' is not declared.    E:\Homes\DotNetNuke_2\Website\admin\Containers\SolPartActions.ascx.vb    119
Warning    15    'Public Function GetPostBackClientEvent(control As System.Web.UI.Control, argument As String) As String' is obsolete: 'The recommended alternative is ClientScript.GetPostBackEventReference. http://go.microsoft.com/fwlink/?linkid=14202'    E:\Homes\DotNetNuke_2\Website\admin\Containers\SolPartActions.ascx.vb    145
Error    16    Name 'ProcessModuleLoadException' is not declared.    E:\Homes\DotNetNuke_2\Website\admin\Containers\SolPartActions.ascx.vb    159
Error    17    Name 'IsAdminControl' is not declared.    E:\Homes\DotNetNuke_2\Website\admin\Containers\Visibility.ascx.vb    135
Error    18    Name 'ProcessModuleLoadException' is not declared.    E:\Homes\DotNetNuke_2\Website\admin\Containers\Visibility.ascx.vb    230
Error    19    Name 'ProcessModuleLoadException' is not declared.    E:\Homes\DotNetNuke_2\Website\admin\Containers\Visibility.ascx.vb    256

Looks like there is either some configuration problem in my development environment even after using the starter kit or there is some problem with the source distribution. I was able to run the binary distribution fine though.

best regards,
Tommi Laukkanen

2/11/2006 11:06 AM

	Simon Rear
5 posts

Re: VSWD Express & DotNetNuke 4 Code Base Rebuilds

Tommi Thanks for the reply,

After a bit more searching I suspect the reason may be that the Visual Studio Web Express only supports Web Application Projects instead of all the other projects that the full blown version supports. If any body here could confirm / expand on this it would help my understanding.

Regards,

Simon

2/12/2006 8:12 AM

	Tommi Laukkanen
2 posts

Re: VSWD Express & DotNetNuke 4 Code Base Rebuilds

Hi Simon,

Yes it is true that web express only supports the web site development. You might be able to build the vb projects with the Visual Basic Express but its separate tool so you can not build the hole thing at once with the express versions. When doing module development you dont need to build the solution but just open the website part in the visual studio web express.

Regarding my building problem I solved it so that I took the install distribution and opened it to the visual studio web express.I was able to rebuild it and create new module with the starter kit templates. After finding hints in the web about module installation I run the scripts in the data provider files under DesktopModules/<ModuleName> directory and then the module was available in the portal. All in all it looks that the module development is quite easy. Only the possibly broken 4.0.2 source distribution is problematic at least in my case.

best regards,
Tommi Laukkanen

Page 1 of 1

Forum

General DotNetN...

Extend It! ( Pr...

VSWD Express & DotNetNuke 4 Code Base Rebuilds