 |
|
|
|
Joined: 12/10/2010
Posts: 4
|
|
|
I just inherited a DNN based website to perform some bug fixes and enhancements. The only thing I was provided with was the website itself - none of the class libraries or a solution file so I can open this up in Visual Studio. I tried downloading the source code, and adding the other required projects to the website in Visual Studio, but it still won't compile and I'm getting hundreds and hundreds of errors. Surely someone else has done this before? Can someone walk me through the way to do this properly?
Thanks.
|
| |
|
|
 | |
|
|
 |
www.wesnetdesigns.com
Joined: 2/18/2005
Posts: 3253
|
|
|
Unless you absolutely must make bug fixes and enhancements to the core framework code, I strongly suggest that you do not attempt this approach. Not only will it be difficult to merge source projects with a working site, maintaining a site with modified core framework during future upgrades will be a real pain. Most of the framework code is compiled into the DotNetNuke.dll assembly. Individual modules are most often compiled into their own assemblies as are the various providers and HttpHandlers. The website itself is just-in-time compiled each time it is loaded. DotNetNuke does not currently support pre-compilation of the website - only the library, providers, HttpHandlers, and other extensions such as modules.
I also hope that in addition to the website files you also have access to or were provided to a backup copy of the installation's database.
Perhaps if you indicate the current version of the site installation, the version of the source code you are trying to work with, and the scope of the bug fixes and enhancements you wish to make I can offer some other suggestions.
Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
|
| |
|
|
| |
|
|
|
Joined: 12/10/2010
Posts: 4
|
|
|
Thanks for your reply.
So I should just be able to open the website the client provided, and modify that?
|
| |
|
|
| |
|
|
|
Joined: 12/10/2010
Posts: 4
|
|
|
OK, so I opened Visual Studio and did "Add Website", and opened up the site provided by the client. Seemed to work fine, but I'm getting a couple of compile errors, for example, this line:
If Not Upgrade.Upgrade.IsNETFrameworkCurrent Then
The compiler is actually telling me the IsNETFrameworkCurrent requires a string parameter.
and...
objPortalController.UpdatePortalInfo(intPortalId, txtPortalName.Text, strLogo, _
txtFooterText.Text, datExpiryDate, optUserRegistration.SelectedIndex, _
optBanners.SelectedIndex, cboCurrency.SelectedItem.Value, _
Convert.ToInt32(cboAdministratorId.SelectedItem.Value), dblHostFee, _
dblHostSpace, intPageQuota, intUserQuota, _
IIf(cboProcessor.SelectedValue = "", "", cboProcessor.SelectedItem.Text).ToString, _
txtUserId.Text, txtPassword.Text, txtDescription.Text, txtKeyWords.Text, _
strBackground, intSiteLogHistory, intSplashTabId, intHomeTabId, intLoginTabId, _
intUserTabId, cboDefaultLanguage.SelectedValue, Convert.ToInt32(cboTimeZone.SelectedValue), _
lblHomeDirectory.Text)
Error 69 Overload resolution failed because no accessible 'UpdatePortalInfo' accepts this number of arguments. C:\Users\David Mitchell\Documents\Work\AllenVanguard\DesktopModules\Admin\SiteLog\Portals\SiteSettings.ascx.vb 698 21 C:\...\AllenVanguard\
Any idea what's going on?
|
| |
|
|
| |
|
|
|
www.wesnetdesigns.com
Joined: 2/18/2005
Posts: 3253
|
|
|
As I indicated earlier, you CANNOT compile the website. It is setup as a dynamically-compiled website project that will be just-in-time compiled automatically when it is loaded. DotNetNuke does not support pre-compilation of the website. Only the core library (DotNetNuke.dll assembly, etc.), various providers and HttpHandlers, and certain modules are compiled.
I would first get a localhost instance of the existing website files and a restore of the database backup which you were hopefully provided up and running (without touching it in VS). Once that is successfull, you can best decide what steps to take next - upgrade to latest version of DotNetNuke framework, modify/add existing content, upgrade or install new modules, etc.
If you want to become more familiar with the DotNetNuke source files and overall architecture, I would suggest installing a separate website on localhost using the 5.06.00 source package. As part of that installation you will be able to build the DotNetNuke solution (VS2010) which includes projects for the core library, and the various providers, HttpHandlers, and support projects. You will also see that in the VS solution build configuration, the website itself (in website folder) is not selected (and should not be selected) to be built.
Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
|
| |
|
|
| |