The following arguments are required and don't have values: RootNamespace, ModuleNamespace, ModuleTestProjectNamespace

Topics: Web Client Software Factory
Mar 8, 2011 at 5:17 PM

I am following instruction of http://blogs.msdn.com/b/mpuleio/archive/2007/03/15/using-the-wcsf-with-an-existing-web-application-projects.aspx to integrate WCSF to my existing web application project. However, when I tried to add Business Module I got error:

Microsoft.Practices.RecipeFramework.RecipeExecutionException: An exception occurred during the binding of reference or execution of recipe CreateModuleCS. Error was: The following arguments are required and don't have values: RootNamespace, ModuleNamespace, ModuleTestProjectNamespace, ModuleInterfaceProjectNamespace, ModuleWebsiteNamespace. Can't continue execution.. 

I have searched and cannot not find solution for this. I had the exact same problem with this unanswered thread: http://webclientguidance.codeplex.com/discussions/48887. and suggestion links on this thread http://webclientguidance.codeplex.com/discussions/68337 are invalid.  I did add

GlobalSection(ExtensibilityGlobals) = postSolution
		 IsWCSFSolution = True
		 IsWCSFSolutionWAP = True
		 RootNamespace = myWebApplication 
	EndGlobalSection
to my sln file. Any suggestion to solve the problem? Thank you!
Li Aishen

Mar 8, 2011 at 5:22 PM
Edited Mar 9, 2011 at 7:57 PM

Forgot mention that I am using Visual Studio 2010 and Web Client Software 2010

Developer
Mar 9, 2011 at 5:10 PM

Hi Li,

You could try reinstalling the Guidance Package to see if it is a problem with the installation. Also, you could examine the contents of the csproj file of your module to check if those attributes are set. For example, on the Customers.csproj file in the Modularity QuickStart there is a section like this:

<RootNamespace>ModularityQuickstart.Customers</RootNamespace>

I hope you find this helpful.

Guido Leandro Maliandi
http://blogs.southworks.net/gmaliandi

Mar 9, 2011 at 7:56 PM

Hi, Guido,

Thank you! I un-installed GAX and web client software factory 2010 first, then reinstalled them, I have still the same problem. I checked the project file of the module that I created: it has like: <RootNamespace>Module5</RootNamespace>

The this new created module is located in Modules, shouldn't this be  <RootNamespace>Modules.Module5</RootNamespace>

I am wondering this is my web application file structure problem. here is my current solution structure:

Solution 'My_Old_WAP'

---Library

---Modules

------module1

------module2

------shell

...

---My_Old_Classes

---My_Old_WAP

Thank you!

 

Mar 9, 2011 at 10:11 PM

I guess that RootNamespace in my sln was not picked up by GAX when I use Web Client Factory-Add Business Module.  I have a legacy web application structure like:

Solution 'My_Old_WAP'

---Solution Items

---My_Old_Classes

---My_Old_WAP

------my legacy files and folders

---Miscellanea

---My_Old_WAP.sln

 

Currently, in my My_Old_WAP.sln, I have 

GlobalSection(ExtensibilityGlobals) = postSolution IsWCSFSolution = True

IsWCSFSolutionWAP = True

  RootNamespace = My_Old_WAP

I noticed the shell project that I added as an existing project has original namespace like"  <RootNamespace>WebClient1.Shell</RootNamespace>, then I changed it to: " <RootNamespace>Modules.Shell</RootNamespace>"

anyway, still the same error: not be able to create a module.

Best regards

Li Aishen

Developer
Mar 10, 2011 at 3:23 PM
Edited Mar 10, 2011 at 3:26 PM

Li,

Have you tried modifying the namespace (or adding the correct one) in all the fields that the error mentions? Also, when you modify the RootNamespace, does the error still mention RootNamespace as one of the missing arguments?

Note that you should probably edit the fields in both the sln and the csproj files.

Thanks,

Guido Leandro Maliandi
http://blogs.southworks.net/gmaliandi

Mar 10, 2011 at 6:23 PM

Guido, 

Thank you! Yes, I tried to put different names of RootNamespace in my sln file such as: My_Old_WAP ( my original web application project namespace), then I tried Modules, and tried MyDir(the folder name of my solution located), none of them works.

Li Aishen

Developer
Mar 11, 2011 at 4:28 PM

Hi Li,

What I was referring to in my previous answer was if you have tried to include the expected values in the ModuleNamespace, ModuleTestProjectNamespace, ModuleInterfaceProjectNamespace and ModuleWebsiteNamespace elements as well.

If you still can't find a solution to this, it would be helpful if you could provide us with a repro sample, so that we can help you find out the cause of your issue.

Thanks,

Guido Leandro Maliandi 
http://blogs.southworks.net/gmaliandi

Mar 15, 2011 at 9:31 PM

Hi, Guido,

Thank you! Sorry to reply you late. Actually I just lost my job. Anyway, Where do you set up the ModuleNamespace,ModuleTestProjectNamespaceModuleInterfaceProjectNamespace and ModuleWebsiteNamespace elements? I tried to set them up at sln file, but it still has the same problem. For example, 

GlobalSection(ExtensibilityGlobals) = postSolution
		 IsWCSFSolution = True
		 IsWCSFSolutionWAP = True
		 RootNamespace = mySolutionRootFolderName
		 ModuleTestProjectNamespace = mySolutionRootFolderName.Modules.Tests

		 ModuleInterfaceProjectNamespace = mySolutionRootFolderName.Modules.Interfaces
		 ModuleWebsiteNamespace = mySolutionRootFolderName.MyOldWebAppFolder
		 		
	EndGlobalSection
Thank you!
Li Aishen

Mar 18, 2011 at 6:21 PM

Hi Li,

After following the steps described in Michael Puleio´s blog post and upgrading the versions of the assemblies that Web Client use, I was able to migrate an existing web site that had no references to WCSF.

You should take into account that I had to upgrade the assembly version of the Microsoft.Practices.EnterpriseLibrary.ExceptionHandling assembly in the Web.Config file in order for the page to work.

You can download a working solution here, so that you can compare it to your solution and fix the necessary parts. Additionally, if you find that you can’t run our sample, it should indicate that your problems are happening due to the environment. Note that we are also using Visual Studio 2010 with the Web Client Software Factory 2010 version as well.

Let me know if this information helps you.

Thanks,

Miguel Bronzovic
http://blogs.southworks.net/mbronzovic