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

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...EventQueue.EventQueueController nowhere to be found!EventQueue.EventQueueController nowhere to be found!
Previous
 
Next
New Post
1/24/2007 5:14 AM
 
John Mitchell wrote

I just downloaded the 4.4 source package and the files are there.

By any chance are you unzipping the package without using the "retain folders" method?

I do know what you mean about how hard it is to keep up with changes in the source though.  Especially if folders are moved around.  My approach is to always start new with each new release, but this is very hard to do if you are also making changes to the core.



Yes, the files are in the 4.4.0 package, but that isnt the problem. The problem is that the files does not seem to exist in the 4.0.2 version, so when I apply the 4.4.4 upgrade package (which does not contain these files either), and try to build, it will generate errors, as it tries to call the EventQueue stuff which just isn't available. So, my conclusion are still the same, that the 4.4.0 upgrade package wont work with 4.0.2 versions, but it will probably work from version that included the EventQueue for the first time.

I do however agree with you that in order to upgrade, one would probably be better of just installing a fresh new sourcepackage, and then use that as a basis instead, but that of course is a lot of work if you are working in such a big project as I am, as there are many new custom made projects to add etc. It's even harder if you have had to make any changes to the Nuke core, as we have been forced to do in this project (not to many, but still, a few).

Perhaps a more thorough upgrade document needs to be created that explains the upgrade more in detail, and when it can not be used?

/pJ
 
New Post
1/24/2007 10:28 AM
 

I'm not sure where you are getting a 4.4.4 version, the latest version I know about is the 4.4.0 version, which has the files.  I hear that Benefactors have access to 4.4.1 and that we will see it soon, maybe that is the one you are talking about?

I think I am understanding what you are getting at though.  If new features are added and you have an old project then how do you sync up the additions (and deletions).

That is a problem I even faced while on the core team.  Even with access to the core source control system I still had to sync those changes manually, or just start new.
I'm not sure if there is much that can be done to help make that any better unless the core team would publish a changed files list.

 


DotNetNuke Modules from Snapsis.com
 
New Post
1/25/2007 3:52 AM
 
The latest SOURE package contains the EventQueue files, but the latest UPGRADE package doesn't, as it only contains the Website part of the package. It does however contain serveral new files that depend on the EventQueue (and probably other stuff also), so when you try to rebuild with a updated Website and a not updated library, you will get errors.

/pJ

PS What must I do to be allowed to post to this forum without moderation? I've been a forum member for something like 3-4 years now, you would think that it would be enough :-)
 
New Post
1/25/2007 9:37 AM
 

 

Ok, I get it now. You are right.  The Upgrade package is only for upgrading a previously deployed site and in theory it would not contain any source, but since we now have runtime compilation I see where you are having into a problem.  As a matter of fact, this makes the problems of keeping the runtime souce in sync much more than just a developers problem.

However, the EventQueue source is not part of the website runtime.  It is part of the class library package that gets compiled before the site is deployed, and will be included in the DotNetNuke.dll in the upgrade package.

In other words, you should not try to rebuild your solution by adding the Upgrade package, you have to use the Source package, and yes that can be difficult.

You'll need to get the attention of a moderator to be able to post without going through the queue. 

 


DotNetNuke Modules from Snapsis.com
 
New Post
1/25/2007 3:54 PM
 
Actually, my main point with this thread was to point out that the documentation needs to be updated regarding updates (funny, eh?) to clearly state that it will only work for sites that are "in production" so to speak and that anyone thinking of using it as a base for further development (ie Visual Studio) should use the soure package instead or run into problems. I would guess that quite a few people already know this, perhaps learnt the hard was as for me, but it's no point having the not knowing run into more problems than necessary.

As you point out multiple times, just starting from scratch is a bit tedious since you will have to set up your development environment from the begining (kind of). We are doing a full Internet Bank using DNN, so there are pleanty of none DNN code and projects besides the DNN ones.

/pJ
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...EventQueue.EventQueueController nowhere to be found!EventQueue.EventQueueController nowhere to be found!


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