Hello Martin,
Did you work with SQL Server or other database? I test such a SQL Server
table in VS.NET 2003:
CREATE TABLE [dbo].[Table1] (
[id] [int] NOT NULL ,
[name] [char] (10) COLLATE Chinese_PRC_CI_AS NULL ,
[Testuni] [uniqueidentifier] NULL
) ON [PRIMARY]
GO
It generate such DataSet:
<xs:complexType>
<xs:sequence>
<xs:element name="id" type="xs:int" />
<xs:element name="name" type="xs:string" minOccurs="0" />
<xs:element name="Testuni" msdata:DataType="System.Guid,
mscorlib, Version=1.0.5000.0, Culture=neutral,
PublicKeyToken=b77a5c561934e089" type="xs:string" minOccurs="0" />
</xs:sequence>
</xs:complexType>
And it can be added to other projects. Is the database or table structure
that cause the difference between us?
Luke
martinwlarsen@newsgroup.nospam - 02 Mar 2005 14:41 GMT
Thanks for your answer, which led me to investigate the xsd.
Because I have VS 2005 installed on the machine and IIS uses the newest
asp.net engine as default it breaks the add reference in vs2003. The xsd for
the webservice dataset field will look like this because the asp.net engine
is running version 2:
<xs:element msdata:DataType="System.Guid, mscorlib, Version=2.0.3600.0,
Culture=neutral, PublicKeyToken=b77a5c561934e089" minOccurs="0"
name="Testuni" type="xs:anyType" />
Which can not be used from VS 2003 as it does not know mscorlib,
Version=2.0.3600.0.
I fixed the issue by changing the ASP.NET version for the webservice folder
in IIS to version 1.1.43222.0.
For following article describes how to do the change:
http://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/prodd
ocs/en-us/Default.asp?url=/resources/documentation/WindowsServ/2003/standard/pro
ddocs/en-us/aaconconfiguringaspnetapplicationforaspnetversion.asp
The scary part is that it means that if I convert the webservice to
VS2005(Framework 2.0) in the future I will break all of my clients unless
they have already been converted.
BRGDS
Martin W. Larsen
> Hello Martin,
>
[quoted text clipped - 24 lines]
>
> Luke
[MSFT] - 03 Mar 2005 02:02 GMT
Hi Martin,
I am glad to hear you have found the problem. Now VS.NET 2005 is just beta
version, we may expect this can be changed in release version.
Luke