Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Why DotNetNuke.WebUtility project still in VB.NET?Why DotNetNuke.WebUtility project still in VB.NET?
Previous
 
Next
New Post
3/28/2015 12:21 AM
 
 Why DotNetNuke.WebUtility project still in VB.NET? Isn't the whole DNN converted to C#?

 

I am getting these errors in 7.5

Error 5 'ClientResourceManager' is not declared. It may be inaccessible due to its protection level. C:\inetpub\wwwroot\DNN75\DNN Platform\DotNetNuke.WebUtility\ClientAPI.vb 699 21 DotNetNuke.WebUtility

Error 6 'ClientResourceManager' is not declared. It may be inaccessible due to its protection level. C:\inetpub\wwwroot\DNN75\DNN Platform\DotNetNuke.WebUtility\ClientAPI.vb 703 21 DotNetNuke.WebUtility

Error 7 'FileOrder' is not declared. It may be inaccessible due to its protection level. C:\inetpub\wwwroot\DNN75\DNN Platform\DotNetNuke.WebUtility\ClientAPI.vb 703 94 DotNetNuke.WebUtility

Error 8 'ClientResourceManager' is not declared. It may be inaccessible due to its protection level. C:\inetpub\wwwroot\DNN75\DNN Platform\DotNetNuke.WebUtility\ClientAPI.vb 706 25 DotNetNuke.WebUtility

Error 9 'FileOrder' is not declared. It may be inaccessible due to its protection level. C:\inetpub\wwwroot\DNN75\DNN Platform\DotNetNuke.WebUtility\ClientAPI.vb 706 107 DotNetNuke.WebUtility

Error 10 'ClientResourceManager' is not declared. It may be inaccessible due to its protection level. C:\inetpub\wwwroot\DNN75\DNN Platform\DotNetNuke.WebUtility\ClientAPI.vb 710 21 DotNetNuke.WebUtility

Error 11 'FileOrder' is not declared. It may be inaccessible due to its protection level. C:\inetpub\wwwroot\DNN75\DNN Platform\DotNetNuke.WebUtility\ClientAPI.vb 710 98 DotNetNuke.WebUtility

Error 12 'ClientResourceManager' is not declared. It may be inaccessible due to its protection level. C:\inetpub\wwwroot\DNN75\DNN Platform\DotNetNuke.WebUtility\ClientAPI.vb 713 25 DotNetNuke.WebUtility

Error 13 'FileOrder' is not declared. It may be inaccessible due to its protection level. C:\inetpub\wwwroot\DNN75\DNN Platform\DotNetNuke.WebUtility\ClientAPI.vb 713 119 DotNetNuke.WebUtility

Error 14 'ClientResourceManager' is not declared. It may be inaccessible due to its protection level. C:\inetpub\wwwroot\DNN75\DNN Platform\DotNetNuke.WebUtility\ClientAPI.vb 717 21 DotNetNuke.WebUtility

Error 15 'ClientResourceManager' is not declared. It may be inaccessible due to its protection level. C:\inetpub\wwwroot\DNN75\DNN Platform\DotNetNuke.WebUtility\ClientAPI.vb 882 17 DotNetNuke.WebUtility


 

 

 
New Post
3/29/2015 11:56 PM
 

I had to fix some bad references in some projects. The way the solution is set up at Github doesn't compile out of the box. 

 
New Post
3/30/2015 4:13 AM
 
Did you follow this http://dnn-connect.org/community/blog...?

When I built it I did not have the problems you describe.

Best wishes,
- Richard
Agile Development Consultant, Practitioner, and Trainer
www.dynamisys.co.uk
 
New Post
3/30/2015 12:15 PM
 

I checked out the branch using svn. I didn't see anything different in the article other using using different tools but that shouldn't matter. The 750 branch should be a self contained solution. References are defined in csproj files and some weren't correct. DotNetNuke.web.mvc wasn't part of the solution. However I am still surprised to see some .vb files.

 
New Post
4/3/2015 3:16 PM
 
FYI ClientAPI was added into the source in 7.4.0 via a community pull request (https://github.com/dnnsoftware/Dnn.Pl...) - Oliver added the source and project references and didnt convert it -however it works fine. As for the feature/7.5.0 branch it seems fine to me, but it may have not been stable when you pulled it down

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Why DotNetNuke.WebUtility project still in VB.NET?Why DotNetNuke.WebUtility project still in VB.NET?


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out