Manager Templates With v2.6

Posts   
 
    
hplloyd
User
Posts: 191
Joined: 29-Oct-2004
# Posted on: 23-Aug-2008 11:58:44   

Hi,

I have been using version 2.0 for some time now with the manager templates on a large commercial product that is now a major success - check out the website for a flavour of what we have built - www.saberanalytics.com

It is now time to move on and develop the next killer app!! I want to upgrade to the latest version of LLBL, but before I do I want to ensure the manager templates still work. so my questions are

  1. if using 2.6 can I still compile code for .NET 2 i.e. without Linq support?
  2. If I do use Linq support will I need to upgrade to Visual Studio 2008?
  3. Will the version 2.0 manager templates work with 2.6, or are there plans to update them - They are so very useful, although I have made a few modifications that I doubt are of any use to anyone else.
  4. I am also interested in the ASP.NET 2.0 GUI generator templates - will these also work under version 2.6?

Many thanks

Huw

daelmo avatar
daelmo
Support Team
Posts: 8245
Joined: 28-Nov-2005
# Posted on: 24-Aug-2008 18:45:55   

hplloyd wrote:

I have been using version 2.0 for some time now with the manager templates on a large commercial product that is now a major success - check out the website for a flavour of what we have built - www.saberanalytics.com

Great. That should be on the Showcases forum

hplloyd wrote:

  1. if using 2.6 can I still compile code for .NET 2 i.e. without Linq support?

Yes

hplloyd wrote:

  1. If I do use Linq support will I need to upgrade to Visual Studio 2008?

Yes you should have VS2008

hplloyd wrote:

  1. Will the version 2.0 manager templates work with 2.6, or are there plans to update them - They are so very useful, although I have made a few modifications that I doubt are of any use to anyone else.

The manager templates aren't officially ported to v2.6 but they work great, I just tested a bit with LLBLGenPro v2.6.

hplloyd wrote:

  1. I am also interested in the ASP.NET 2.0 GUI generator templates - will these also work under version 2.6?

Yes, they are available at v2.6 download section.

David Elizondo | LLBLGen Support Team
hplloyd
User
Posts: 191
Joined: 29-Oct-2004
# Posted on: 25-Aug-2008 15:09:42   

Many thanks for the information....

I have downloaded v2.6 alongside v2.0 and copied across all the templates, tasks etc from my 2.0 folder to my 2.6 folder, and have been running a few tests (with the manager templates)

I have a project that generates perfectly in V2.0, but in V2.6 the same project does not generate - I think the issue is to do with the ProjectFileCreator task that I run against my BusinessObject folder - I am fairly confident that everything is generated perfectly up to that point, so it is falling over at the last stage!!

The task I have to generate the project file looks like this

<task name="VisualStudio.NetProjectFileCreator" assemblyFilename="SD.LLBLGen.Pro.TaskPerformers.dll" taskPerformerClass="SD.LLBLGen.Pro.TaskPerformers.ProjectFileCreator" isOptional="true" description="">
            <supportedPlatforms/>
            <supportedTemplateGroups>
                <templateGroup name="Adapter"/>
            </supportedTemplateGroups>
            <dependencies/>
            <parameters>
                <parameter name="destinationFolder" defaultValue="" isOptional="false" description="The folder to generate the project file in, relative to the destination root folder."/>
                <parameter name="binRootFolder" defaultValue="BusinessObjects\"  isOptional="true" description=""/>
                <parameter name="alterWhenExistent" defaultValue="false" isOptional="true" description=""/>
                <parameter name="filenameFormat" defaultValue="[projectName].BusinessObjects.[extension]proj" isOptional="true" description=""/>
                <parameter name="templateID" defaultValue="SABER_BusinessObjectsProjectTemplate" isOptional="true" description=""/>
                <parameter name="alwaysTarget" defaultValue="2005" isOptional="true" description=""/>
                <parameter name="clearFileCacheAfterwards" defaultValue="true" isOptional="true" description=""/>
                <parameter name="useRootNameSpaceForProjectName" defaultValue="true" isOptional="true" description=""/>
            </parameters>
            </task>

And the template used looks like this:


<Project DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
  <PropertyGroup>
    <ProjectType>Local</ProjectType>
    <ProductVersion>8.0.50727</ProductVersion>
    <SchemaVersion>2.0</SchemaVersion>
    <ProjectGuid>{<[ProjectGuid]>}</ProjectGuid>
    <Configuration Condition=" '$(Configuration)' == '' ">Debug</Configuration>
    <Platform Condition=" '$(Platform)' == '' ">AnyCPU</Platform>
    <ApplicationIcon>
    </ApplicationIcon>
    <AssemblyKeyContainerName>
    </AssemblyKeyContainerName>
    <AssemblyName><[ProjectName]>.BusinessObjects</AssemblyName>
    <AssemblyOriginatorKeyFile>
    </AssemblyOriginatorKeyFile>
    <DefaultClientScript>JScript</DefaultClientScript>
    <DefaultHTMLPageLayout>Grid</DefaultHTMLPageLayout>
    <DefaultTargetSchema>IE50</DefaultTargetSchema>
    <DelaySign>false</DelaySign>
    <OutputType>Library</OutputType>
    <RootNamespace><[RootNamespace]></RootNamespace>
    <RunPostBuildEvent>OnBuildSuccess</RunPostBuildEvent>
    <StartupObject>
    </StartupObject>
    <FileUpgradeFlags>
    </FileUpgradeFlags>
  </PropertyGroup>
  <PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Debug|AnyCPU' ">
    <OutputPath><[BinRootFolder]>bin\Debug\</OutputPath>
    <AllowUnsafeBlocks>false</AllowUnsafeBlocks>
    <BaseAddress>285212672</BaseAddress>
    <CheckForOverflowUnderflow>false</CheckForOverflowUnderflow>
    <ConfigurationOverrideFile>
    </ConfigurationOverrideFile>
    <DefineConstants>DEBUG;TRACE</DefineConstants>
    <DocumentationFile>
    </DocumentationFile>
    <DebugSymbols>true</DebugSymbols>
    <FileAlignment>4096</FileAlignment>
    <NoStdLib>false</NoStdLib>
    <NoWarn>
    </NoWarn>
    <Optimize>false</Optimize>
    <RegisterForComInterop>false</RegisterForComInterop>
    <RemoveIntegerChecks>false</RemoveIntegerChecks>
    <TreatWarningsAsErrors>false</TreatWarningsAsErrors>
    <WarningLevel>4</WarningLevel>
  </PropertyGroup>
  <PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Release|AnyCPU' ">
    <OutputPath><[BinRootFolder]>bin\Release\</OutputPath>
    <AllowUnsafeBlocks>false</AllowUnsafeBlocks>
    <BaseAddress>285212672</BaseAddress>
    <CheckForOverflowUnderflow>false</CheckForOverflowUnderflow>
    <ConfigurationOverrideFile>
    </ConfigurationOverrideFile>
    <DefineConstants>TRACE</DefineConstants>
    <DocumentationFile>
    </DocumentationFile>
    <DebugSymbols>false</DebugSymbols>
    <FileAlignment>4096</FileAlignment>
    <NoStdLib>false</NoStdLib>
    <NoWarn>
    </NoWarn>
    <Optimize>true</Optimize>
    <RegisterForComInterop>false</RegisterForComInterop>
    <RemoveIntegerChecks>false</RemoveIntegerChecks>
    <TreatWarningsAsErrors>false</TreatWarningsAsErrors>
    <WarningLevel>4</WarningLevel>
  </PropertyGroup>
  <ItemGroup>
    <Reference Include="SD.LLBLGen.Pro.ORMSupportClasses.NET20, Version=2.0.0.0, Culture=neutral, PublicKeyToken=ca73b74ba4e3ff27, processorArchitecture=MSIL">
        <SpecificVersion>False</SpecificVersion>
        <HintPath><[RuntimeLibraryHintPath]></HintPath>
    </Reference>

    <Reference Include="System">
      <Name>System</Name>
    </Reference>
    <Reference Include="System.Data">
      <Name>System.Data</Name>
    </Reference>
    <Reference Include="System.Xml">
      <Name>System.XML</Name>
    </Reference>
  </ItemGroup>
  <ItemGroup>
<[FileIncludes]>
    <AppDesigner Include="Properties\" />
  </ItemGroup>
  <ItemGroup>
    <Folder Include="Properties\" />
  </ItemGroup>
  <Import Project="$(MSBuildBinPath)\Microsoft.CSHARP.Targets" />
  <PropertyGroup>
    <PreBuildEvent>
    </PreBuildEvent>
    <PostBuildEvent>
    </PostBuildEvent>
  </PropertyGroup>
</Project>

But when I generate the project I get thee error (in the exception viewer)

Name cannot begin with the '[' character, hexadecimal value 0x5B. Line 73, position 14.

And the stack trace looks like this:

-----[Core exception]-------------------- at System.Xml.XmlTextReaderImpl.Throw(Exception e) at System.Xml.XmlTextReaderImpl.Throw(String res, String[] args) at System.Xml.XmlTextReaderImpl.Throw(Int32 pos, String res, String[] args) at System.Xml.XmlTextReaderImpl.ParseQName(Boolean isQName, Int32 startOffset, Int32& colonPos) at System.Xml.XmlTextReaderImpl.ParseElement() at System.Xml.XmlTextReaderImpl.ParseElementContent() at System.Xml.XmlTextReaderImpl.Read() at System.Xml.XmlLoader.LoadNode(Boolean skipOverWhitespace) at System.Xml.XmlLoader.LoadDocSequence(XmlDocument parentDoc) at System.Xml.XmlLoader.Load(XmlDocument doc, XmlReader reader, Boolean preserveWhitespace) at System.Xml.XmlDocument.Load(XmlReader reader) at System.Xml.XmlDocument.LoadXml(String xml) at System.Xml.XmlDocument.set_InnerXml(String value) at SD.LLBLGen.Pro.TaskPerformers.ProjectFileCreator.ConstructProjectFileContents(StringBuilder outputText, String projectName, IGenerator executingGenerator, TargetVersion versionToTarget, String binRootFolder, String fullPath) at SD.LLBLGen.Pro.TaskPerformers.ProjectFileCreator.Perform(IGenerator executingGenerator, ITask taskDefinition, Dictionary2 parameters) at SD.LLBLGen.Pro.ApplicationCore.Tasks.Task.Perform(IGenerator executingGenerator, LogNode parentNode) at SD.LLBLGen.Pro.ApplicationCore.Tasks.TaskGroup.Perform(IGenerator executingGenerator, LogNode parentNode) at SD.LLBLGen.Pro.ApplicationCore.Tasks.TaskGroup.Perform(IGenerator executingGenerator, LogNode parentNode) at SD.LLBLGen.Pro.GeneratorCore.Generator.Start(ITaskGroup tasksToExecute, Project projectDefinition, Language languageToUse, Platform platformToUse, List1 templateBindingsToUse, String templateGroupToUse, ApplicationConfiguration configurationSettings)

has something changed in V2.6? What am I doing wrong?

Many thanks

hplloyd
User
Posts: 191
Joined: 29-Oct-2004
# Posted on: 25-Aug-2008 17:19:02   

No problem,

I was referencing the old version of SD.LLBLGen.Pro.ORMSupportClasses.NET20

Problem solved