Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

About

News Press Releases News Coverage Press KitCareersContact DNN

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 ForumsStoreStoreAddressEdit.acx.cs not foundAddressEdit.acx.cs not found
Previous
 
Next
New Post
12/13/2007 5:06 PM
 
James Reynolds

Joined: 11/5/2007
Posts: 9

Gilles,

I was able to do exactly as your post says to do....using the source of both dnn 4.7 and the store 2.1. This was successful. I was able to compile the store solution and the entire dnn project.

But when I use the dnn template (DotNetNuke Web Application Framework) and install the store module, I can't get the project to compile or the DotNetNuke.Store.sln. Is there a workaround for this? Are there files missing from DotNetNuke Web Application Framework template that the store solution needs to compile successfully?

I'm using the template to create my initial web application because I don't really need to have the complete source of dnn. I don't need to modify any of the core components.

Does this make sense?
 
New Post
12/13/2007 5:52 PM
 
James Reynolds

Joined: 11/5/2007
Posts: 9

This might be helpful info...

When I create my web application using the dnn framework template, I store the files in the default VS 2005 folders which is (C:/../My Documents/Visual Studio 2005/WebSites/..). After installing the store module, I navigated to the Store folder which is (C:/../My Documents/Visual Studio 2005/WebSites/ApplicationName/DesktopModules/Store). I navigated further into the Store folder and found that some of the project file names where not complete. For example, I navigated to (..DesktopModules/Store/Providers/AddressProviders/DefaultAddressProvider/Providers/SqlDataProvider) and the project file is named 'DOTNET~1.CSP'. This file should be named 'DotNetNuke.Store.Providers.Address.DefaultAddressProvider.SqlDataProvider.csproj'. I can't rename the file (too long or something). Same thing with the project file names for ShippingProviders and TaxProviders. When I tried to open the DotNetNuke.Store.sln, these were the only files that wouldn't load; therefore, I couldn't build the solution successfully.
 
New Post
12/14/2007 8:16 AM
 
Gilles Le Pigocher


Joined: 10/11/2003
Posts: 1966

Hi,

This is a well know problem related to Windows. Every .net software have this problem on all Windows versions! It's a legacy problem with Win32 API. You can read here the offical Microsoft comment from the BCL Team.

The only workaround is to install your dnn instance near than the root disk, like C:\DNN. I will try to use shorter names in the future but this will not solve all cases. Because if your dnn is installed on C:\Inetpub\www\DotNetNukeFrameworkV462\MyLongCompanyName\MyLongProjectName this path use more than 70 characters on 248!

Gilles

We (team members) are Humans offering their knowledge, their work and their spare time FOR FREE to benefit the community. It would be so particularly appreciated that your messages begin with "Hello" and end with "Thank you" or any other form of politeness. Ask yourself what your reaction would be, if you were approached by me (a total stranger) on the street to ask you something without saying "Hello" nor "Thank you"? After several years of services dedicated to the community, I begin to be tired to read requests without any form of politeness.
 
New Post
12/14/2007 11:35 AM
 
James Reynolds

Joined: 11/5/2007
Posts: 9

Thanks Gilles. That's interesting. I didn't know that about long file names and paths.

Back to my problem...yesterday, after I found that those files names were too long, I did try creating a new project (using the DotNetNuke Web Applicaiton Framework template) and saving the project directly at c:\ApplicationName. I built the project successfully. I then ran the project (View in Browser) and installed the Store module source. The Store module installed successfully. I went back to my project folder directory to check all of the Store module project files and everything was fine. I went to my project in VS 2005 and tried to build the project again (this time with the Store module) and I got the AddressEdit error.

I guess there is no way to get the Store module to compile with the DotNetNuke Web Applicaiton Framework template. Is there?

The only way I did get everything to work was to use the Store module Source AND the DotNetNuke Source. 
 
New Post
12/14/2007 1:43 PM
 
Jan Durian


Joined: 6/5/2004
Posts: 181

Hi,
maybe my experience can help a little:

  1. I installed Dnn install version 4.5.5 into <drv>:\Dotnetnuke_2 folder (see dnn documentation), then Store source version and I can build the Store project without any problems.
  2. I upgraded to Dnn version 4.7.0 because with this core version I don’t see in event viewer “path too long” errors anymore. I hope it’s corrected not hidden …
 
 Page 3 of 6
Previous1234...6Next 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsStoreStoreAddressEdit.acx.cs not foundAddressEdit.acx.cs not 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