Problem to load mojoportal.net40.sln solution in recent VS 2013

This forum is only for questions or discussions about working with the mojoPortal source code in Visual Studio, obtaining the source code from the repository, developing custom features, etc. If your question is not along these lines this is not the right forum. Please try to post your question in the appropriate forum.

Please do not post questions about design, CSS, or skinning here. Use the Help With Skins Forum for those questions.

This forum is for discussing mojoPortal development

You can monitor commits to the repository from this page. We also recommend developers to subscribe to email notifications in the developer forum as occasionally important things are announced.

Before posting questions here you might want to review the developer documentation.

Do not post questions about design, CSS, or skinning here. Use the Help With Skins Forum for those questions.

This thread is closed to new posts. You must sign in to post in the forums.

3/3/2015 2:19:01 PM

Schakim

Total Posts 18

View Posts

Re: Problem to load mojoportal.net40.sln solution in recent VS 2013

Yes I have Debug selected, and the other DropDown has "Mixed Platforms". After reboot I now have "549 errors in 211 files" instead, in the statusbar. To the left it now says "Ready" but how can I check it was rebuilt?

There is also an "Error List" pane in lower part of window, which seem to be different to the 549 errors. There is just 1 error and 26 warnings. The error there is:

Error 1 The command "C:\Projects\wc\mojoportal\LanguageRemover\bin\Debug\LanguageRemover.exe C:\Projects\wc\mojoportal\Web\App_GlobalResources" exited with code 9009. LanguageRemover

Among the 549 errors there are things like:

"Cannot find usage of Class 'cleared'" and Cannot find Skin 'cleared'" in this line from BingMapModule.ascx

<portal:EmptyPanel id="divCleared" runat="server" CssClass="cleared" SkinID="cleared"></portal:EmptyPanel>

and in BlogCompare.aspx "Cannot find ContentPlaceHOlder 'phHead' in in the Master page '~/App_MasterPages/DialogMaster.Master'

and an ASP.NET runtime error for that page 'Could not load file or assembly 'AjaxControlToolkit, version 4.5.7.1213, ... or one of its dependencies. The located assembly's manifest definition does not match the assembly reference.

Just as some samples as it's a lot to type... but maybe it gives you an idea?

3/4/2015 8:21:56 AM

Schakim

Total Posts 18

View Posts

Re: Problem to load mojoportal.net40.sln solution in recent VS 2013

Wait a minute, I wonder if the small widget at far right of the statusbar, reporting "549 error in 211 files", isn't provided by one of the Add-ons I have installed, Resharper and CodeSmart, and that it reports this simply because it doesn't understand what we are doing here. It appears as if those errors all have their origin from direct or derived references done in the <% Page Directive %> which aren't available until the solution have been built and these pages exists at their proper place - or something like that as I haven't wrapped my head around everything yet. But is that a reasonable observation?

I guess I will just have to run the web site and see what happens, but I seem to have stuck my nose into a flu here and simply have to put it aside for a few days while riding out a fever taking hold...

3/4/2015 8:53:54 AM

Joe Audette

Total Posts 18439

View Posts

Re: Problem to load mojoportal.net40.sln solution in recent VS 2013

that sounds like a reasonable theory, only the one single error sounds expected and it is irrelevant.

I suggest copy the mojoportal.sln file to a new location and rename it like mojoportal.custom.sln or whatever, then copy it back to the original folder.

open the new custom solution, right click the LanguageRemover project and choose remove to remove it from the solution, it is not needed and was resulting in one build error which was just a distraction.

rebuild the solution

copy the user.config.sample file as user.config and set a connection string there for a new empty mssql db

launch the mojoportal.Web project

errors are expected at this point since the db is empty, just click continue on any error in the debugger, it should eventually redirect to /Setup which will run the sql scripts to solve the errors

if you decide to develop custom features that plugin to mojoportal, you can now add your own projects to the custom solution. any custom code should be in your own projects so this is the standard way to get started.

by coincidence I'm also coming down with scratchy throat and low grade fever, spent yesterday afternoon in bed and plan to stay there all day today as well

You must sign in to post in the forums. This thread is closed to new posts.