community-content

Forum Replies Created

Viewing 15 posts - 1,186 through 1,200 (of 9,648 total)
  • Author
    Posts
  • Hi,

    May be there a cross reference? You could build and deploy from the beginning?
    Look, I have some solution – in my case there are
    1. Schemas project it’s a “base” project
    2. Maps project – has a reference to schemas’s dll
    3. Orchestrations project – has a reference to schemas’ and to maps’ projects dll’s

    The base of them is schemas, for deploying it – I delete references from maps and orchestrations, after deploy I add reference of schemas to maps, deploy maps, after it I add reference from Orchestrations to schemas and maps and deploy.
    In my case it’s not a problem – cause I don’t add schemas  to the project every 5 minutes. Maybe this is a way for you too. Orchestrations could be deployed as many times as I need – without a problem.

    Thanks for your answers

     

    @Zx7R: I now tried to change the reference to Dll’s. Now I have some less problems. But still I have in one project this problem.

    TFS is not installed. I use Tortoise SVN for source control. It doesn’t lock the file. I allready checked this with process monitor.

    The event log doesn’t say anything.

    And yes, I am administrator. So it isn’t a permission issue.

     

    I now tried to make for each project a single solution and build one after the other. Result: I was able to build at least the half of the projects.

    in reply to: Creating an XML Schema for an excel file #24898

    You can write Disassembler for BizTalk receive pipeline to receive excel file and write the code to read excel data. I am not sure whether there are other ways than using excel oledb component. If you want to follow this way, you need to make some logic to link your excel file to OLEDG datasource (probably another replica of excel file). However this is really difficult to maintain in case of concurrency.

    PS: There is one solution to receive/send excel in BizTalk but you will need to pay for this. click here to see, also you can download the trial version if you feel okay.. I am not sure how it works internally though.
    Another alternative is to create some services (windows service) to convert .xls file to .csv or directly xml and drop into the biztalk receive location.
    Or If it is possible to receive csv files/text file/xml file directly, this is the great way in my view.

    Apart from Yonathan’s suggestion, 

    Sometimes I restart the visual studio solution and it works after Cleaning the solution and rebuilding again (may be batch build). Check if you have any postbuild event written for the project which might be causing problem. 

    Sometimes I restart the visual studio solution and it works after Cleaning the solution and rebuilding again (may be batch build). Check if you have any postbuild event written for the project which might be causing problem. 

    Hi,

    1. Do yo ureference to Project or to Dll? Tyr to change reference to dll if you use reference to project.

    2. Do you use TFS or some another source controlling program? try to open each project which makes you problems and remove “read only” checkbox (it stays thouh undercontrol).

    3. Anything interesting in event log?

    4. Are you administrator on your machine?

    Just for information.

    My development environment is:

    – Windows Server 2008

    – BizTalk Server 2009

    – Visual Studio 2008

     

    in reply to: Creating an XML Schema for an excel file #24891

    Hi,

     

       You are probably better off using this commercial solution:

    http://www.fpoint.com/biztalk/default.aspx

     

       Daniel.

     

    in reply to: Destination File Name in an Email body #24890

    Hi,

     

       I hope you enjoyed the day off… I am not German, but I’ve enjoyed visiting Germany in the past. 🙂

     

       The XML code you pasted above does not tell how and where the HTML file is output, so can you paste the C# script?

     

       Daniel.

     

    in reply to: Loop shape in Orchestration #24889
    in reply to: Calling a "plex" web service? #24888

    Hi Greg,

    I had already tried the ?WSDL approach, but it did not work when trying to generate the schema. Also navigating to the url does also not display the WSDL, so am unsure as to whether this is provided in this way by a Plex webservice – my previous experiences have all been with asmx web services.

    I am not in a position to contact the provider (yet) as this was just prep-work for a possible project so I can’t yet bother their IT staff 🙂

    Thanks for the input.

    Stu.

    in reply to: Destination File Name in an Email body #24885

    Hi Daniel

    Sorry for late answer but we had a bank holiday in Germany yesterday.
    Are you a German too?

    Anyway, please find below the code of the XML2HTMLSendPipeline.btb I couldn’t find a path or a name there the file will be saved as html. Can you?

    Do you need the C# script too?

    Many thanks for your help.

    —————-
    <?xml version=”1.0″ encoding=”utf-16″?>
    <Document xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance&#8221;
    xmlns:xsd=”http://www.w3.org/2001/XMLSchema&#8221;
    PolicyFilePath=”BTSTransmitPolicy.xml” MajorVersion=”1″
    MinorVersion=”0″>
      <Description />
      <Stages>
        <Stage CategoryId=”9d0e4101-4cce-4536-83fa-4a5040674ad6″>
          <Components />
        </Stage>
        <Stage CategoryId=”9d0e4107-4cce-4536-83fa-4a5040674ad6″>
          <Components>
            <Component>
              <Name>Microsoft.BizTalk.Component.XmlAsmComp</Name>
              <ComponentName>XML assembler</ComponentName>
              <Description>XML assembler component.</Description>
              <Version>1.0</Version>
              <Properties>
                <Property Name=”EnvelopeDocSpecNames”>
                  <Value xsi:type=”xsd:string” />
                </Property>
                <Property Name=”EnvelopeSpecTargetNamespaces”>
                  <Value xsi:type=”xsd:string” />
                </Property>
                <Property Name=”DocumentSpecNames”>
                  <Value xsi:type=”xsd:string” />
                </Property>
                <Property Name=”DocumentSpecTargetNamespaces”>
                  <Value xsi:type=”xsd:string” />
                </Property>
                <Property Name=”XmlAsmProcessingInstructions” />
                <Property Name=”ProcessingInstructionsOptions”>
                  <Value xsi:type=”xsd:int”>0</Value>
                </Property>
                <Property Name=”ProcessingInstructionsScope”>
                  <Value xsi:type=”xsd:int”>0</Value>
                </Property>
                <Property Name=”AddXmlDeclaration”>
                  <Value xsi:type=”xsd:boolean”>true</Value>
                </Property>
                <Property Name=”TargetCharset”>
                  <Value xsi:type=”xsd:string” />
                </Property>
                <Property Name=”TargetCodePage”>
                  <Value xsi:type=”xsd:int”>0</Value>
                </Property>
                <Property Name=”PreserveBom”>
                  <Value xsi:type=”xsd:boolean”>true</Value>
                </Property>
                <Property Name=”HiddenProperties”>
                  <Value
    xsi:type=”xsd:string”>EnvelopeSpecTargetNamespaces,DocumentSpecTargetNam
    espaces,TargetCodePage</Value>
                </Property>
              </Properties>
              <CachedDisplayName>XML assembler</CachedDisplayName>
              <CachedIsManaged>true</CachedIsManaged>
            </Component>
          </Components>
        </Stage>
        <Stage CategoryId=”9d0e4108-4cce-4536-83fa-4a5040674ad6″>
          <Components>
            <Component>
     
    <Name>Microsoft.BizTalk.SDKSamples.Pipelines.XslTransformComponent.XslTr
    ansformer</Name>
              <ComponentName>XSL Transform Component</ComponentName>
              <Description>XSL Transform Pipeline Component</Description>
              <Version>1.0</Version>
              <Properties>
                <Property Name=”XsltFilePath”>
                  <Value xsi:type=”xsd:string”>E:\BizTalk\Computerlinks
    Orchestrations\RONNY\RonnysProjekt\transform.xsl</Value>
                </Property>
              </Properties>
              <CachedDisplayName>XSL Transform Component</CachedDisplayName>
              <CachedIsManaged>true</CachedIsManaged>
            </Component>
          </Components>
        </Stage>
      </Stages>
    </Document>
    —————-

     

    in reply to: Problem with polling TableChangedEvent in Oracle 10g #24883

    We did not want to have to many messages of this type at once.

    We did need to have room and instances for other message types.

    in reply to: Generating schemas – consuming WCF Adapter service. #24882

    Hmm.. The second Serialization schema was also deleted, but I saw in “All artefacts” same primitive types schemas – they belong to Biztalk itself.

    So, can I delete Serialization schemasafter creating schemas for WCF service?

    in reply to: Generating schemas – consuming WCF Adapter service. #24881

    Seems that it’s working (two added WCF services with one, Serialization schema).

    Do I need this Serialization schema at all?

    – Though, another question (maybe also will be solved by myself):

    If I generate schemas for SQL Wcf-Adapter, from stored procedures, each collection of schemas have DataSet – that on a first glance look same. But – there some mini-guids (some keys maybe?) which I think they influence on different schemas (for different stored procedures).

    Is there a way to leave only one DataSet schema and it will work?

Viewing 15 posts - 1,186 through 1,200 (of 9,648 total)