James
New Member
Posts:23
 |
|
Steve Provencher
Moderator
Advanced Member
Posts:683
|
| 08 Aug 2011 11:04 PM |
|
A Patch will be out hopefully on 8/9/11 for DNN 6 and will address this as well in other DNN versions. |
|
|
|
|
James
New Member
Posts:23
|
| 09 Aug 2011 07:36 PM |
|
I just upgraded to your newest release. Now when I go to "manage form", I get this:
A critical error has occurred.Unable to cast object of type 'System.Web.UI.WebControls.SubMenuStyle' to type 'System.Web.UI.WebControls.MenuItemStyle'. |
|
|
|
|
Code 5
Moderator
Advanced Member
Posts:941
|
| 09 Aug 2011 07:43 PM |
|
What is your operating system environment. DNN Version etc. .NET versions on the server |
|
|
|
|
James
New Member
Posts:23
|
| 09 Aug 2011 07:49 PM |
|
DNN 6.0.0;
DotNet Framework 4.0
Hosting through PowerDNN; not sure of OS version. |
|
|
|
|
Code 5
Moderator
Advanced Member
Posts:941
|
| 09 Aug 2011 09:33 PM |
|
Form Master requires .NET Framework 2.0 which must be installed when .NET Framework 3.5 SP1 is installed on the server. .NET Framework 3.5 SP1 is recomended for DotNetNuke |
|
|
|
|
James
New Member
Posts:23
|
| 09 Aug 2011 09:41 PM |
|
Well, this might be problematic. I have only two options available to me:
4.0.30319.1 or...
2.0.50727.4927
I have several other modules I'm using that require 3.5. If I move down to 2.0, then I will break them. I'm in a catch-22. I have been using you guys for years with terrific success. I would hope we could find some workaround.
|
|
|
|
|
Steve Provencher
Moderator
Advanced Member
Posts:683
|
| 09 Aug 2011 10:30 PM |
|
The pre-requisites for .NET Framework 3.5 SP1 are .NET Framework 2.0 SP2 and .NET Framework 3.0 SP2. So if you have .NET Framework 3.5 SP1 installed on your server you must have .NET Framework 2.0 as it cannot be installed without it. |
|
|
|
|
James
New Member
Posts:23
|
| 09 Aug 2011 10:33 PM |
|
You must not have caught my previous post. I ONLY have the ability to install either 4.0 OR 2.0; not 3.5.
Are you not planning on supporting 4.0? Why does 4.0 not allow for controls built with previous versions? |
|
|
|
|
Steve Provencher
Moderator
Advanced Member
Posts:683
|
| 09 Aug 2011 11:06 PM |
|
>> Form Master requires .NET Framework 2.0
So you cannot install 2.0 if 4.0 is installed? I have sever al servers where all .NET Frameworks are installed with no issue.
>>I have several other modules I'm using that require 3.5.
How are you planning to support these modules if you cannot install 3.5? |
|
|
|
|
Steve Provencher
Moderator
Advanced Member
Posts:683
|
| 10 Aug 2011 04:27 PM |
|
After thinking about this a bit, here's what I think
You are seeing the .NET version availability in IIS which only lists 4.0.30319.1 and 2.0.50727.4927
When you select 2.0.50727.4927 and if you have .NET 3.0 and .NET 3.5 installed on the server, those will be available to the Web Application even though you cannod see that in IIS.
DotNetNuke Recommends using .NET Framework 3.5 sp1 http://www.dotnetnuke.com/Resources...ments.aspx
You can set this by using 2.0.50727.4927 in IIS and making sure all the Framework versions are installed. |
|
|
|
|
James
New Member
Posts:23
|
| 10 Aug 2011 05:38 PM |
|
Well Steve. I did as you suggest and "YES" the DNN reports it now has 3.5 installed. I have tested all my other modules and they all appear to be working just fine. I had one little glitch with a setting in the Web.Config file, but that has been remedied.
Now I have a differenct issue. It seems I have lost the ability to Export and Import. This is a critical feature for me. Is this something that was eliminated or something that can easily be fixed?
I do appreciate all the support you guys provide. This is why I have used you for so long. Your module is outstanding and your support top notch. |
|
|
|
|
Steve Provencher
Moderator
Advanced Member
Posts:683
|
| 10 Aug 2011 06:15 PM |
|
Even though I have told the DotNetNuke installer what Form Master Supports it did not set it properly From my .dnn file <|supportedFeatures|> <|supportedFeature type="Portable"/|> <|/supportedFeatures|> See this post http://www.code5systems.com/Support...fault.aspx |
|
|
|
|
James
New Member
Posts:23
|
| 10 Aug 2011 06:24 PM |
|
I had seen that before and forgot about it. That did the trick. All is working! Thank you thank you!!! |
|
|
|
|
James
New Member
Posts:23
|
| 10 Aug 2011 06:29 PM |
|
Oops! One more thing I just found. I suspect it has to do with remnants of .NET 4.0 in the web.config file. I hope you can help. Man, am I a pain in the butt or what? At least I clicked on all the options to make sure I was thorough! |
|
|
|
|
James
New Member
Posts:23
|
|
James
New Member
Posts:23
|
| 10 Aug 2011 07:22 PM |
|
My examples got parsed. I emailed them to your generic email address. I hope you got them. |
|
|
|
|
James
New Member
Posts:23
|
| 10 Aug 2011 09:49 PM |
|
I got it! When I moved back from .NET 4.0 to .NET 3.5 two entries in the web.config did not reverse itself. For those of you with similar issues I did the following:
In the runtime section I changed the line
<|bindingredirect oldversion="1.0.0.0-1.1.0.0" newversion="4.0.0.0">
to
I did this in two places. The lines were there, just commented out.
Wow, what an adventure. |
|
|
|
|
James
New Member
Posts:23
|
| 10 Aug 2011 09:50 PM |
|
well, it keeps parsing out my entries.
I changed the binding redirect references from 4.0.0 back to the 3.5. the lines are there, just comment out the 4.0.0 references and uncomment the 3.5 references. There are TWO. |
|
|
|
|
Code 5
Moderator
Advanced Member
Posts:941
|
| 10 Aug 2011 10:49 PM |
|
James thanks for the followup. I tried to fix your post but some stuff was missing. |
|
|
|
|