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

HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsEventsEventsErrors in events.sln fileErrors in events.sln file
Previous
 
Next
New Post
9/19/2006 7:50 PM
 
I have the DNN 4.3.4 solution file as my DNN project. I just overwrote the original events module that came with 3.0.2 with the source from Events 3.2 module. When I open up my DotNetNuke.sln file with visual studio it shows no errors, however when i open up the Events.sln file I have 3 errors which i believe are making it not possible for me to create an install file with a few changes I made to files like EventMonth.ascx.vb (as well as some of the other .vb files), I believe that when you build the solution the EventMonth.resx file is updated with the changes made to the .vb file (correct me if I'm wrong) and I need to create a new install so i can install the new module with the changes i made.

Here are the three errors i get:
1. Type 'Framework.Providers.ProviderConfiguration' is not defined
2. Type 'Framework.Providers.Provider' is not defined
3. 'Common' is not a member of 'DotNetNuke'

Does anyone know what I may be missing?
 
New Post
2/6/2007 12:07 AM
 

You could always add dotnetnuke to fix those errors but my guess is you are missing a reference.

change 'Framework.Providers.ProviderConfiguration'  to 'Dotnetnuke.Framework.Providers.ProviderConfiguration'

change 'Framework.Providers.Provider'  to 'Dotnetnuke.Framework.Providers.Provider'

add dotnetnuke in front of common.

That will/should clear your errors.

 
New Post
3/1/2007 3:13 PM
 

OK, here is some clarity on this issue:

1.  We are using DNN 4.4.1, and the latest release of the Events module, circa March 2006.

2.  We are using Visual Studio 2005.

3.  When we open the EVENTS.SLN file, Visual Studio tells us that this file was created in an OLDER version of Visual Studio, and that it needs to be converted. 

4.  We choose to convert the file, since Visual Studio 2005 will refuse to open the file without conversion.

5.  We "Start the website without debugging."  Visual Studio rebuilds the project, and throws the errors listed in the first post of this thread.

I am guessing that the DNN core framework is a Visual Studio 2005 project (since the DotNet framework 2.0 was not supported in Visual Studio 2003), but the Events module was developed in Visual Studio 2003 (supported in DotNet 2.0 via backward compatibility). 

Do we really need two versions of Visual Studio on our development machines to make this work, or can we do a proper conversion on the Events module and stay in Visual Studio 2005 for all of our development work?  (I prefer the latter approach, for several reasons)

 
New Post
3/1/2007 3:27 PM
 

We are in release on the last version of the Events Module for DNN 3&4.  The latest release (in the certification process now) will support both DNN 3&4.  However, next stop migrate the module to DNN 4 (sunset DNN 3 support).  So, given that, I am working on converting the module to a complete 2005 solution...it will be a WAP (not a WSP)...I still think pretty big when it comes to development...I like the idea of being able to extend (and protect) code using the WAP model...there are probably a few advantages of using WAP, but I tend to think "large scale apps" and how to create re-usable libraries....so anyhow...the answer is we're working on it and even though DNN does not yet fully support AJAX, we are planning on these type of features.

 
New Post
3/6/2007 12:39 PM
 
Seems the first 3 messages had something to do with a broken reference to the DotNetNuke.dll, deleting the reference, then recreating seems to have cleared all of my errors.

Although I do get this message when opening the solution file.
"Unable to open the Web 'http://localhost/DNN32Debug/DotNetNuke.vbproj'. Could not find a Web server at 'localhost' on port 80. Please check to make sure that the web server name is valid and your proxy settings are set correctly. If you are sure everything is correct, the Web server may be temporarily out of service."

Possibly has something to do with IIS?
 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsEventsEventsErrors in events.sln fileErrors in events.sln file


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