[xsd-users] RE: XSD 3.2.0 beta1 released

[Rizzuto, Raymond]

Boris,

I understand about the .msi including xerces, though I was surprised about the libxsd vs include directory names.

To answer your second question, yes, the .rules in the beta work correctly.

Ray

-----Original Message-----
From: Boris Kolpackov [mailto:boris at codesynthesis.com]
Sent: Thursday, September 04, 2008 4:28 PM
To: Rizzuto, Raymond
Cc: xsd-users at codesynthesis.com
Subject: Re: [xsd-users] RE: XSD 3.2.0 beta1 released

Hi Ray,

Thanks for the information. My comments are below.

Rizzuto, Raymond <Raymond.Rizzuto at sig.com> writes:

> - directory tree differences from 3.1.0 (libxsd vs include)
> - no xerces
>    o copied the include/xercesc from 3.1 to 3.2's libxsd/xercesc
>    o copied the xerces dll's from 3.1's bin directory to 3.2's bin directory
>    o copied the lib directory from 3.1's tree to same location in 3.2

These differences are due to you using the .msi installer for 3.1.0 while
for betas we only provide the .zip package which contains only XSD proper.
With the final release we will make both .msi and .zip available.


> I'm also again having the issue I reported previously where xsd will
> rebuild the output files every time I compile.  At first I was pointing
> to the wrong set of rules files, but then I fixed the rules directory
> path in VC and selected it for the project, and now that is working
> correctly also.

Just to confirm: once you have pointed VC to the .rules files from
the beta, everything started working ok, right?

Boris

IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses.