Root Namespace for VB Project

Hot Topic

Is there any way to time procedures in vb2005.
DataExchangeService Attribute in Beta 2.2
UDP & RTP Filter Lacking In DirectShow
Microsoft Windows User Experience: Official Guidelines for User Interface Developers and Designers
More simplistic conditions and branches
Going-Live and Persistence
Microsoft Outlook .OAB
Tracing persistance erors
vista search technical documentation - where can I find it?
Exchange data in state machine scenario

Windows Vista

Create new condition rule from the designer
What I'm doing wrong in web.config?
Is it a Bug?
MenuStrip is still missing from UISpy
Web services and runtime compilation
IsExecutable
A small help!!
Capturing correct output parameters
Query on SQL Tracking service for WWF
Error adding a custom activity to a workflow

Root Namespace for VB Project

It seems that I am required to have a Root Namespace specified in the project options for my Workflow Assembly. If I do not have a root namespace specified I receive the following error:

option 'rootnamespace' requires ':<string>'

I have currently only tried this in VB.NET and not C#, so I don't know if this happens in both languages.

Is this some sort of a bug I like to expicitly declare my namespace for each class and remove the root namespace.

Answer this question

Root Namespace for VB Project

  • andy18

    Are the standalone Go-Live downloads updated with the each CTP release or are they fixed to a version (i.e. Jan CTP) From what I understand, development would be done using the WinFX download and when it came time for deployment I would need to deploy the standalone Go-Live version of the assemblies. If the Go-Live assemblies are not updated along with the WinFX CTP release then I truely am locked into the Jan CTP and must live the bugs and issues that are present. That would I cannot upgrade to the Feb CTP.

    Phil

  • roundcrisis

    I can verify that this is a bug in the Beta 2 of the Windows Workflow foundation [the version installed with the Jan CTP]. I get the identical error when leaving out the Root Namespace on a workflow project and specifying the namespace as part of the workflow .vb files:

    option 'rootnamespace' requires ': <string>'

    vbc : Command Line

    Line 0: Column 0

  • person person person

    This used to be a bug in beta1, but should have been fixed in the latest beta2 release.



    Shelly

  • Henry Wu

    Yes this indeed was an issue in Beta2 and has been fixed in later builds.

    Thanks,

    Chethan

  • Skyblue1

    By the latest Beta 2 release, do you mean the Feb CTP Because it is still a bug in the Jan CTP. With that in mind, does the Go-Live license cover the Feb CTP release or does it only apply to the Jan CTP release My point is, if the go-live license only covers the Jan CTP version, then I am unable to upgrade to the Feb CTP (and any future releases) and must live with the bugs and issues in the Jan CTP.

  • forumnewbie2006

    Shelly's comment re Beta2 was most likely referring to the Beta2 of Windows Workflow Foundation, available via http://www.microsoft.com/downloads/details.aspx FamilyId=A2151993-991D-4F58-A707-5883FF4C1DC2&displaylang=en and in the WinFX February CTP.

    Regarding Go-Live Licenses, please note that the available Go-Live Licenses do not apply to the WinFX download/install. It only applies to the standalone downloads/installs for Beta 2 of Windows Workflow Foundation and Windows Communication Foundation. You can find more information on the go-live site: http://msdn.microsoft.com/winfx/getthebeta/golive/default.aspx and on the FAQ page of the go-live site: http://msdn.microsoft.com/winfx/getthebeta/golive/faq/default.aspx

    Anna

    This posting is provided "AS IS" with no warranties, and confers no rights



  • Root Namespace for VB Project
Answer this question