Mike Stuart
wading in the water
Posts:25
 |
| 06-27-2011 08:02 PM |
|
After Dynamic Registration is installed, we get
Compiler Error on Links Module
BC30002: Type 'Net.WebProxy' is not defined
Line 87: If Not Integer.TryParse(DotNetNuke.Entities.Host.Host.ProxyPort, proxyPort) Then Throw New InvalidCastException("ProxyPort", "Invalid proxy port in dotnetnuke host settings. Port must be an integer!")
Line 88:
Line 89: Dim proxy As New Net.WebProxy(DotNetNuke.Entities.Host.Host.ProxyServer, proxyPort)
Line 90: webClient.Proxy = proxy
Line 91: End If
If we Remove the Dynamic Registration DLLs from Bin directory and it compiles
|
|
|
|
|
Mike Stuart
wading in the water
Posts:25
|
| 06-27-2011 09:07 PM |
|
changing line 90 in the App_Code/Links/LinksController.vb file
From: Dim proxy As New Net.WebProxy(DotNetNuke.Entities.Host.Host.ProxyServer, proxyPort)
Into: Dim proxy As New System.Net.WebProxy(DotNetNuke.Entities.Host.Host.ProxyServer, proxyPort)
Fixes it.
|
|
|
|
|
Chad Nash
Posts:5260
|
| 06-28-2011 07:27 AM |
|
Hi Mike,
Can you tell me what version of DNN you are running on? Specifically, is this the DNN 6 Beta or what version? I am not directly familiar with any errors at all and we don't really control the code for this so it might be something we/you want to report to DNN if its happening in the 6.0 beta.
-Chad
|
|
|
|
|
Chad Nash
Posts:5260
|
| 06-28-2011 07:53 AM |
|
Hi. I asked DNN Corp folks about this and this is what they told me:
"DNN Links has been a WAP project for quite a few versions, so this is either NOT the core Links module or the Links module is very old in that site."
I do know that we have not had any other reports of this though.
-Chad |
|
|
|
|
Mike Stuart
wading in the water
Posts:25
|
| 06-28-2011 08:04 AM |
|
FYI - It's the new DNN 6 (BETA) version.
So something to keep your eye on, as it gets to release.
Just letting you all know about the issue, there are two references in the BETA version of Links, where someone left off the System reference and it creates the issue.
They provide the code with it, so it's easy enough to make the edits.
|
|
|
|
|
Mike Stuart
wading in the water
Posts:25
|
| 06-28-2011 08:04 AM |
|
FYI - It's the new DNN 6 (BETA) version.
So something to keep your eye on, as it gets to release.
Just letting you all know about the issue, there are two references in the BETA version of Links, where someone left off the System reference and it creates the issue.
They provide the code with it, so it's easy enough to make the edits.
|
|
|
|
|
Mike Stuart
wading in the water
Posts:25
|
| 06-28-2011 08:05 AM |
|
BETA Version of the Links module |
|
|
|
|
mike schepker
skipping stones
Posts:6
|
| 07-21-2011 10:57 AM |
|
I just upgraded the links module to 6.0 (which has now been released) on my dnn 5.6.3 site and got this error. Any updates on this? |
|
|
|
|
mike schepker
skipping stones
Posts:6
|
| 07-21-2011 11:17 AM |
|
looks like updating to Links 6.00.02 solved the issue. didn't realize there was an update to Links 6.0 as the project page on dotnetnuke.com still listed 6.00.00 as the latest version. |
|
|
|
|
Scott
new to the springs
Posts:2
|
| 10-03-2011 03:17 AM |
|
I was having the same problem with my DNN community version 6.0.1.
Installing DNN Links Module 6.0.2 before upgrading Dynamic Registration fixed my issue as well. |
|
|
|
|
equaTEK Interactive
wading in the water
Posts:26
|
| 07-19-2012 06:51 AM |
|
I got the same error installing onto DNN 6.1.2. I had Links 6.0.0 in place. The suggested change to LinksController.vb fixed the error.
I looked into upgrading to Links 6.0.2, but it will not allow it on this version of DNN. I would need to upgrade DNN first. |
|
|
|
|
Chad Nash
Posts:5260
|
| 07-25-2012 02:21 PM |
|
Thanks for posting the update and code changes!
-Chad
|
|
|
|
|