Common code generation

[DBC User]

Hi,

This is a very simple question so please bare with my ignorance on
this. I want to write a piece of code which does a common task
(independent) which reads xml input and process something and then
create an xml output. I want to share this code with different groups,
I have 2 questions on this
1. How do I go about building one like this and is there a link
somewhere I can read about this?
2. When I make changes to my code how do I distribute my changed to
other development groups?

Thanks.

[sloan]

One way is an xml to xml transformation using xsl.

OR you can read thru the xml.

Here is how to do #1.

http://sholliday.spaces.live.com/Blog/cns!A68482B9628A842A!148.entry



"DBC User" <db*****@gmail.comwrote in message
news:11**********************@n2g2000hse.googlegro ups.com...

Hi,

This is a very simple question so please bare with my ignorance on
this. I want to write a piece of code which does a common task
(independent) which reads xml input and process something and then
create an xml output. I want to share this code with different groups,
I have 2 questions on this
1. How do I go about building one like this and is there a link
somewhere I can read about this?
2. When I make changes to my code how do I distribute my changed to
other development groups?

Thanks.

[Ben Voigt [C++ MVP]]

"DBC User" <db*****@gmail.comwrote in message
news:11**********************@n2g2000hse.googlegro ups.com...

Hi,

This is a very simple question so please bare with my ignorance on
this. I want to write a piece of code which does a common task
(independent) which reads xml input and process something and then
create an xml output. I want to share this code with different groups,
I have 2 questions on this
1. How do I go about building one like this and is there a link
somewhere I can read about this?
2. When I make changes to my code how do I distribute my changed to
other development groups?

If all users have network access to you, you could expose a web service.

Probably though, you'll just want to distribute the assembly. You can
create .msi files to make sure that older versions are correctly removed
during an upgrade. There's also OneClick deployment, but I think it is more
for applications than reusable components.

One possible solution is to have a text file on your web server than
contains the version number of the latest release. Then you can put some
code in that only runs in debug builds, compares the current version to the
version on the web, and tells the programmers when a new version is
available.