|
Home > Archive > BizTalk Server General > July 2005 > More Info and progress on the same
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
More Info and progress on the same
|
|
| BizTalk Benjamin 2005-07-22, 5:50 pm |
| I came across a post on another site which said that it may be because the
map was opened in another editor (like TextPad) which could have inserted
some unrecognisable characters in it . The solution that the poster
recommended was to open the map file in various editors and save them, open
and close VS a few times.
I opened and closed it in UltraEdit and then restarted VS and managed to
open one of the maps which is a direct XML to XML mapping and has no
functoids. The other one is a flat file to XML mapping and has some inline C#
functoids which refuses to open. So now i am forced to re-do the entire map.
Why on earth is the editor so sensitive to file formats ? its terribly
annoying
- benjy
| |
| Tomas Restrepo \(MVP\) 2005-07-22, 5:50 pm |
| Hi benjamin,
>I came across a post on another site which said that it may be because the
> map was opened in another editor (like TextPad) which could have inserted
> some unrecognisable characters in it . The solution that the poster
> recommended was to open the map file in various editors and save them,
> open
> and close VS a few times.
>
> I opened and closed it in UltraEdit and then restarted VS and managed to
> open one of the maps which is a direct XML to XML mapping and has no
> functoids. The other one is a flat file to XML mapping and has some inline
> C#
> functoids which refuses to open. So now i am forced to re-do the entire
> map.
>
> Why on earth is the editor so sensitive to file formats ? its terribly
> annoying
Both the Schema and map editors are fairly picky. I've had good experiences
with making sure that when editing the files in external editors they are
saved with UTF-16 encoding with a BOM, and making sure the <?xml?> directive
agrees with said encoding.
--
Tomas Restrepo
tomasr@mvps.org
http://www.winterdom.com/
| |
| Scott Colestock 2005-07-22, 5:50 pm |
| (Make sure you set these file types for binary storage if you are using
SourceSafe, too - this is a common problem, since SourceSafe doesn't support
UTF-16 for text.)
Scott Colestock
"Tomas Restrepo (MVP)" <tomasr@mvps.org> wrote in message
news:u62mUwtjFHA.3448@TK2MSFTNGP12.phx.gbl...
> Hi benjamin,
>
>
> Both the Schema and map editors are fairly picky. I've had good
> experiences with making sure that when editing the files in external
> editors they are saved with UTF-16 encoding with a BOM, and making sure
> the <?xml?> directive agrees with said encoding.
>
>
> --
> Tomas Restrepo
> tomasr@mvps.org
> http://www.winterdom.com/
>
| |
| BizTalk Benjamin 2005-07-23, 5:49 pm |
| Scott , Tomas,
Thanks for the feedback. I'll make sure we set the encoding right if we open
the file in external editors. We are using SubVersion (or will be shortly) so
at least the Sourcesafe problem wont be there.
cheers
Benjy
"Scott Colestock" wrote:
> (Make sure you set these file types for binary storage if you are using
> SourceSafe, too - this is a common problem, since SourceSafe doesn't support
> UTF-16 for text.)
>
> Scott Colestock
>
> "Tomas Restrepo (MVP)" <tomasr@mvps.org> wrote in message
> news:u62mUwtjFHA.3448@TK2MSFTNGP12.phx.gbl...
>
>
>
| |
| BizTalk Benjamin 2005-07-25, 8:12 am |
| hey y'all,
Just to let you know that we had created a brand new map last week (due to
all the problems with corruption) and made sure we didnt even touch it with
another editor. Guess what? the same error message turned up this
morning...Cant understand it ...
cheers
benjy
"BizTalk Benjamin" wrote:
[vbcol=seagreen]
> Scott , Tomas,
> Thanks for the feedback. I'll make sure we set the encoding right if we open
> the file in external editors. We are using SubVersion (or will be shortly) so
> at least the Sourcesafe problem wont be there.
>
> cheers
> Benjy
>
> "Scott Colestock" wrote:
>
|
|
|
|
|