MonoX support board

Start the conversation, ask questions and share tips and solutions with fellow developers.

Non-registered users can only browse through our support boards. Please register now if you want to post your questions. It takes a second and it is completely free. Alternatively, you can log in without registration using your credentials at major sites such as Google, Microsoft Live, OpenId, Facebook, LinkedIn or Yahoo.

Upgrading to 4.5 (Closed) (Mono Support )

Viewed 52825 time(s), 14 post(s) 10/17/2011 5:40:03 PMby shawndg

Related topics

shawndg

shawndg

10/17/2011 5:40:03 PM
Ok guys..

I am attempting to upgrade and running into a few issues..

First, login status control on my custom header page needed altered..
Once I got that working, now I got some new errors..

Looks like namespace changed..

something to do with this..
PortalWebPartZoneTableless

new way:

<portal:PortalWebPartZoneTableless HeaderText="Right part zone" ID="rightPartZone" runat="server" Width="100%" ChromeTemplateFile="RightColumn.htm" ShowChromeForNonAdmins="false">
<ZoneTemplate>
</ZoneTemplate>
</portal:PortalWebPartZoneTableless>

old way...

<portal:PortalWebPartZone HeaderText='LeftFooterZone' ID="LeftFooterZone" runat="server" Width="100%" ChromeTemplateFile="">
<ZoneTemplate>
</ZoneTemplate>
</portal:PortalWebPartZone>


I had luck on some of my pages with reming them out but I am having some problems with my default.aspx.

any ideas of changes that may be breaking my upgrade ? I used the patch file

This content has not been rated yet. 
1871 Reputation 252 Total posts
denis

denis

10/17/2011 6:15:12 PM
This should work after you recompile the solution, as the namespace for both PortalWebPartZone and the new PortalWebPartZoneTableless is the same. It is possible that VS didn't change the declaration of the Web part zone in the designer.cs file for some reason, so please double check that.
This content has not been rated yet. 
7207 Reputation 956 Total posts
shawndg

shawndg

10/17/2011 6:36:09 PM
ok it turns out thats not the problem..

the old one still is in there..
<portal:PortalWebPartZone HeaderText="Content zone" ID="contentPartZonea" runat="server" Width="100%" ChromeTemplateFile="LeftColumn.htm" ShowChromeForNonAdmins="false">
<ZoneTemplate>
</ZoneTemplate>
</portal:PortalWebPartZone>

I looked in the namespace, and I see there are now two namespaces the new one and my old one..
I prefer to stick with my old one at the moment because I am using divs and have no reason at the moment to use tables.

Ok..so now I dont get.. why it works if I remove that and dont with it.. when I have the code above in my page I get the following error.

An unhandled exception was generated during the execution of the current
web request. Information regarding the origin and location of the
exception can be identified using the exception stack trace below.

Stack Trace:

[NullReferenceException: Object reference not set to an instance of an object.]
MonoSoftware.MonoX.ApplicationSettings.get_WebPartVerbRenderMode() +109
MonoSoftware.MonoX.PortalWebPartZone.OnInit(EventArgs e) +16
System.Web.UI.Control.InitRecursive(Control namingContainer) +132
System.Web.UI.Control.InitRecursive(Control namingContainer) +420
System.Web.UI.Control.InitRecursive(Control namingContainer) +420
System.Web.UI.Control.InitRecursive(Control namingContainer) +420
System.Web.UI.Control.InitRecursive(Control namingContainer) +420
System.Web.UI.Control.InitRecursive(Control namingContainer) +420
System.Web.UI.Control.InitRecursive(Control namingContainer) +420
System.Web.UI.Control.InitRecursive(Control namingContainer) +420
System.Web.UI.Control.InitRecursive(Control namingContainer) +420
System.Web.UI.Control.InitRecursive(Control namingContainer) +420
System.Web.UI.Control.InitRecursive(Control namingContainer) +420
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1969
This content has not been rated yet. 
1871 Reputation 252 Total posts
shawndg

shawndg

10/17/2011 8:05:23 PM
Ok.. O copied the latest web config thinking it may be a issue..

On the default.aspx page I am getting this error..

Personalization is not enabled and/or modifiable. The
Enabled property must be set to true, and a registered personalization
provider must be selected. The current user must be granted the right to
modify personalization state.

This content has not been rated yet. 
1871 Reputation 252 Total posts
denis

denis

10/17/2011 8:07:47 PM
This one is easy: you need to sync the <appsettings> section of the web.config. You will notice several new settings at the bottom of this section in the new version, just copy them to your web.config.
Additionally, please make sure that your App_Templates/Default/ChromeTemplates are also synchronized.
This content has not been rated yet. 
7207 Reputation 956 Total posts
shawndg

shawndg

10/18/2011 1:23:45 PM
Hi Denis,

I even tried copying over the webconfig from the patch and just editing it to make it connect to the database, but it still is giving me this error.

Tried using my old file, and syncing settings.. I am a bit over whelmed at the moment..

Any chance you guys can lend me a hand with this ?

I am going to keep fighting with it, but so far no luck.

I also added the following to my original web config app settings:

<!-- Indicates if this is a WebPI Installation -->
<add key="WebPIInstallation" value="false" />
<!-- Default redirect URL for mobile clients. If empty, no redirect are performed unless this is set at the page level. -->
<add key="DefaultMobileRedirectUrl" value="/MonoX/Mobile/Default.aspx" />
<!-- jQuery reference path for mobile pages and controls. Change it to use other jQuery versions. Note that you can use different versions of jQuery for mobile and desktop versions of your site. -->
<add key="jQueryMobileBaseReferencePath" value="http://code.jquery.com/jquery-1.6.1.min.js" />
<!-- jQuery mobile reference path. -->
<add key="jQueryMobileReferencePath" value="/MonoX/Scripts/Mobile/jquery.mobile-1.0b1.min.js" />
<!-- Web part verb render mode - titlebar or menu. -->
<add key="WebPartVerbRenderMode" value="Titlebar" />
<!-- Verb button type - link, image, button. -->
<add key="WebPartTitleBarVerbButtonType" value="Image" />

which are changes I see between the new version and the old version..

I am still getting a error though..

I even tried using win diff and going thru the entire file and syncing anything up I felt was outdated.
the web config file looks pretty good.. but I am stumped on why its not working..

I figured out that anything that contains portal or a web part don't work..

Personalization is not enabled and/or modifiable. The
Enabled property must be set to true, and a registered personalization
provider must be selected. The current user must be granted the right to
modify personalization state.

I was able to login, using the login page but then when it forwarded me to the default page.aspx i got the same error..
I then navigated to a page without any portals on it that works when not logged in and then I was greeted with another error..

Value cannot be null.
Parameter name: relativeUrl
This content has not been rated yet. 
1871 Reputation 252 Total posts
khorvat

khorvat

10/18/2011 1:29:15 PM
Hi,

can you give us a full stack trace for this error ?

Thanks
This content has not been rated yet. 
15993 Reputation 2214 Total posts
shawndg

shawndg

10/18/2011 1:39:18 PM
First one when i navigate to the default.aspx page..

Server Error in '/' Application.

Personalization is not enabled and/or modifiable.
The Enabled property must be set to true, and a registered
personalization provider must be selected. The current user must be
granted the right to modify personalization state.

Description: An unhandled exception occurred during
the execution of the current web request. Please review the stack trace
for more information about the error and where it originated in the
code.

Exception Details: System.InvalidOperationException:
Personalization is not enabled and/or modifiable. The Enabled property
must be set to true, and a registered personalization provider must be
selected. The current user must be granted the right to modify
personalization state.

Source Error:
An unhandled exception was generated during the execution of the current
web request. Information regarding the origin and location of the
exception can be identified using the exception stack trace below.


Stack Trace:
[InvalidOperationException: Personalization is not enabled and/or modifiable. The Enabled property must be set to true, and a registered personalization provider must be selected. The current user must be granted the right to modify personalization state.]
System.Web.UI.WebControls.WebParts.WebPartPersonalization.EnsureEnabled(Boolean ensureModifiable) +245
System.Web.UI.WebControls.WebParts.WebPartManager.CloseOrDeleteWebPart(WebPart webPart, Boolean delete) +73
System.Web.UI.WebControls.WebParts.WebPartManager.CloseOrphanedParts() +222
System.Web.UI.WebControls.WebParts.WebPartManager.OnPageLoadComplete(Object sender, EventArgs e) +16
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +3628

Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.1

This content has not been rated yet. 
1871 Reputation 252 Total posts
shawndg

shawndg

10/18/2011 1:41:39 PM
Now, I navigate to login.aspx.. able to login..

I then login and then it forwards me back to default.aspx and now I am greeted with a new error below.
I navigate to any page, and this error now shows up all over the site.

Value cannot be null.
Parameter name: relativeUrl

Description: An unhandled exception occurred during
the execution of the current web request. Please review the stack trace
for more information about the error and where it originated in the
code.

Exception Details: System.ArgumentNullException: Value cannot be null.
Parameter name: relativeUrl

Source Error:
An unhandled exception was generated during the execution of the current
web request. Information regarding the origin and location of the
exception can be identified using the exception stack trace below.

Stack Trace:
[ArgumentNullException: Value cannot be null.
Parameter name: relativeUrl]
System.Web.UI.Control.ResolveClientUrl(String relativeUrl) +620
MonoSoftware.MonoX.Utilities.PageUtility.InjectJQueryUIHeaders(Page page) +49
MonoSoftware.MonoX.MasterPages.Main.OnInit(EventArgs e) +124
System.Web.UI.Control.InitRecursive(Control namingContainer) +491
System.Web.UI.Control.InitRecursive(Control namingContainer) +250
System.Web.UI.Control.InitRecursive(Control namingContainer) +250
System.Web.UI.Control.InitRecursive(Control namingContainer) +250
System.Web.UI.Control.InitRecursive(Control namingContainer) +250
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1660

Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.1
This content has not been rated yet. 
1871 Reputation 252 Total posts
khorvat

khorvat

10/18/2011 2:53:19 PM
Hi,

in this second error you are missing jQueryUI URL from the web.config appSettings, can you please check if you have correct files on the disk (sync the urls in the config and on the disk) ?

Regards
This content has not been rated yet. 
15993 Reputation 2214 Total posts
1 2