03-22-05 12:47 PM
Hi,
I have had problems like this in the past.
First, look in your GAC and right click on the assembly name that you are
trying to change. Make sure that this is point to the assembly you are
expecting!
Search on you box, make sure that there are not multiple assemblies present
on your local PC.
A simple way to make a change to a schema and then deploy it, in a dev
environment, is to do the following
1. Compile the project.
2. Browse to the newly compiled assembly (note the date and time is
reflecting the newly compiled output)
3. Open a separate folder window and browse to your GAC
4. Drag and drop the assembly into your GAC..
5. Reboot the BizTalk Server process.
Once you have done this, you should be picking up the correct version.
- Mike Watson
"siddharthkhare@hotmail.com" wrote:
> Hi All,
> does biztalk cache schemas some where?
>
> I changed one of the scheema in my project but it some how keeps using
> old schema .
>
> I have tried following
> 1)stopped all services ,even restarted the biztalk server machine.
> 2)completely undeployed and redeployed the biztalk project.
> 3)incremented the version of project and schema.
>
> Still when i step through the orchestration the value of the newly
> added attribute is null.
> I could see that in promoted properties.
>
> Also this orchestration and schema are published as web service in my
> project.
> When i add a reference of this schema in my client project,proxy class
> has the new attribute i have added.
>
> I am sure ,i am assigning value to this attribute in the client.Also
> this attribute has a default value of it's own .
> so there is no reason for it to be blank unless biztalk some how is
> using old schema?
> appreciate if some one could tell why this might be happening.
> Thanks
> siddharth
>
>
[ Post a follow-up to this message ]
|