473,543 Members | 3,135 Online
Bytes | Software Development & Data Engineering Community
+ Post

Home Posts Topics Members FAQ

Serializing Class with Unqualified Root Element and Default Namespace attribute

I'm trying to serialize (using XmlSerializer.S erialize) a class that I generated from an XSD schema using XSD.EXE /c.

The problem I'm running into is that the root element needs to be unqualified, and the default namespace needs to be included on it
as an attribute. The schema I'm using is this:

<xs:schema
xmlns:x="urn:sc hemas-microsoft-com:office:exce l"
xmlns:html="htt p://www.w3.org/TR/REC-html40"
xmlns:ss="urn:s chemas-microsoft-com:office:spre adsheet"
xmlns:o="urn:sc hemas-microsoft-com:office:offi ce"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:c="urn:sc hemas-microsoft-com:office:comp onent"
attributeFormDe fault="unqualif ied"
targetNamespace ="urn:schema s-microsoft-com:office:spre adsheet"
elementFormDefa ult="unqualifie d">
<xs:import namespace="urn: schemas-microsoft-com:office:offi ce" />
<xs:import namespace="urn: schemas-microsoft-com:office:exce l" />
<xs:import namespace="urn: schemas-microsoft-com:office:comp onent" />
<xs:element name="Workbook" >...
<xs:complexType >
<xs:sequence>
<xs:element ref="o:Document Properties" />
<xs:element ref="o:OfficeDo cumentSettings" />
<xs:element ref="x:ExcelWor kbook" />

But when I use Serialize() I get this:

<?xml version="1.0" encoding="utf-8"?>
<ss:Workbook
xmlns:x="urn:sc hemas-microsoft-com:office:exce l"
xmlns:c="urn:sc hemas-microsoft-com:office:comp onent"
xmlns:ss="urn:s chemas-microsoft-com:office:spre adsheet">...

Which is close, but not close enough.

I tried specifying the default namespace in the call to Serialize(), but it didn't have any effect, on either the qualification on
the Workspace node or the lack of the xmlns attribute on the node.

- Mark

Specifically, I need this:

<Workbook
xmlns="urn:sche mas-microsoft-com:office:spre adsheet"
xmlns:x="urn:sc hemas-microsoft-com:office:exce l"
xmlns:c="urn:sc hemas-microsoft-com:office:comp onent"
xmlns:ss="urn:s chemas-microsoft-com:office:spre adsheet">

Mar 12 '07 #1
9 6451
Mark Olbert wrote:
But when I use Serialize() I get this:

<?xml version="1.0" encoding="utf-8"?>
<ss:Workbook
xmlns:x="urn:sc hemas-microsoft-com:office:exce l"
xmlns:c="urn:sc hemas-microsoft-com:office:comp onent"
xmlns:ss="urn:s chemas-microsoft-com:office:spre adsheet">...

Which is close, but not close enough.
Specifically, I need this:

<Workbook
xmlns="urn:sche mas-microsoft-com:office:spre adsheet"
xmlns:x="urn:sc hemas-microsoft-com:office:exce l"
xmlns:c="urn:sc hemas-microsoft-com:office:comp onent"
xmlns:ss="urn:s chemas-microsoft-com:office:spre adsheet">
Semantically there is no difference between the two snippets, it does
not matter in terms of XML and namespaces whether a namespace is used as
the default namespace or with a prefix.

Can you show us the relevant C# or VB.NET class definition of the
objects you serialize? There are attributes that set the namespace and
the Serialize method has a third argument that maps prefixes to
namespace URI so this class

[XmlRoot(Namespa ce =
"urn:schema s-microsoft-com:office:spre adsheet", ElementName = "Workbook")]
public class Foo
{
public Foo() { }
}

with this code

Foo foo = new Foo();
XmlSerializer serializer = new XmlSerializer(t ypeof(Foo));
serializer.Seri alize(Console.O ut, foo);

serializes as

<Workbook xmlns:xsi="http ://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http ://www.w3.org/2001/XMLSchema"
xmlns="urn:sche mas-microsoft-com:office:spre adsheet" />

while using this code

XmlSerializerNa mespaces namespaces = new
XmlSerializerNa mespaces();
namespaces.Add( "ss",
"urn:schema s-microsoft-com:office:spre adsheet");
serializer.Seri alize(Console.O ut, foo, namespaces);

it serializes as
<ss:Workbook xmlns:ss="urn:s chemas-microsoft-com:office:spre adsheet" />
--

Martin Honnen --- MVP XML
http://JavaScript.FAQTs.com/
Mar 12 '07 #2
Hi Mark

According to your description, what you need is the root element should be
unqualified. If I have misunderstood anything here, please feel free to let
me know.

The XSD schema which you posted in newsgroup is fine.

It seems like you Serialize the WorkBook class conjunction with
XmlSerializerNa mespaces.
Public void Serialize (XmlWriter xmlWriter, Object o,
XmlSerializerNa mespaces namespaces)
Would you please past some code snippet about how did you serialize the
WorkBook Class?

As far as I know, there are two ways you can use to serialize the root
element as unqualified.
Senaro 1:
Stream writer = new FileStream("Wor kbook.xml", FileMode.Create );
XmlSerializerNa mespaces xsnx = new XmlSerializerNa mespaces();
xsnx.Add("", " urn:schemas-microsoft-com:office:spre adsheet");
xsns.Add(...); // other namespaces
XmlSerializer serializer = new XmlSerializer(t ypeof(Workbook) );
serializer.Seri alize(writer, objWorkbook, xsnx);

Senaro 2:
Stream writer = new FileStream("Wor kbook.xml", FileMode.Create );
XmlSerializer serializer = new XmlSerializer(t ypeof(Workbook) );
serializer.Seri alize(writer, objWorkbook);
Hope this helps.
Sincerely,
Wen Yuan

Mar 12 '07 #3
Martin,

>Semantically there is no difference between the two snippets, it does not matter in terms of XML and namespaces whether a namespace is used as
the default namespace or with a prefix.
Unfortunately, it appears to matter a great deal to Microsoft Excel. In testing on both Excel XP and Excel 2007, not having that
xmlns="..." attribute prevents the file from being parsed. Personally, and not knowing much about XML, I think having two attributes
that point at the same namespace (i.e., xmlns="..." and xmlns:ss="<same >") strikes me as weird...but apparently not to the folks who
wrote Excel :).
>Can you show us the relevant C# or VB.NET class definition of the objects you serialize? There are attributes that set the namespace and
the Serialize method has a third argument that maps prefixes to namespace URI so this class
[System.CodeDom. Compiler.Genera tedCodeAttribut e("xsd", "2.0.50727. 42")]
[System.Serializ ableAttribute()]
[System.Componen tModel.Designer CategoryAttribu te("code")]
[System.Xml.Seri alization.XmlTy peAttribute(Ano nymousType=true )]
[System.Xml.Seri alization.XmlRo otAttribute(Nam espace="urn:sch emas-microsoft-com:office:spre adsheet", IsNullable=fals e)]
public partial class Workbook
{
}

and

XmlSerializer serializer = new XmlSerializer(t ypeof(Workbook) );

XmlSerializerNa mespaces ns = new XmlSerializerNa mespaces();
ns.Add("x", "urn:schema s-microsoft-com:office:exce l");
ns.Add("c", "urn:schema s-microsoft-com:office:comp onent");
ns.Add("html", "http://www.w3.org/TR/REC-html40");
ns.Add("ss", "urn:schema s-microsoft-com:office:spre adsheet");

serializer.Seri alize(tw, this, ns); // this is a Workbook object

generates:

<?xml version="1.0" encoding="utf-8"?>
<ss:Workbook xmlns:x="urn:sc hemas-microsoft-com:office:exce l" xmlns:html="htt p://www.w3.org/TR/REC-html40"
xmlns:c="urn:sc hemas-microsoft-com:office:comp onent" xmlns:ss="urn:s chemas-microsoft-com:office:spre adsheet">
<Worksheet ss:Name="Sheet1 ">

which doesn't work because the default xmlns tag is missing. Not adding the "ss" namespace to namespaces generates:

<?xml version="1.0" encoding="utf-8"?>
<Workbook xmlns:x="urn:sc hemas-microsoft-com:office:exce l" xmlns:html="htt p://www.w3.org/TR/REC-html40"
xmlns:c="urn:sc hemas-microsoft-com:office:comp onent" xmlns="urn:sche mas-microsoft-com:office:spre adsheet">
<Worksheet d2p1:Name="Shee t1" xmlns:d2p1="urn :schemas-microsoft-com:office:spre adsheet" xmlns="">

which doesn't work because the Worksheet element redefines the default namespace to "". FYI, the Worksheet class definition is as
follows:

[System.CodeDom. Compiler.Genera tedCodeAttribut e("xsd", "2.0.50727. 42")]
[System.Serializ ableAttribute()]
[System.Componen tModel.Designer CategoryAttribu te("code")]
[System.Xml.Seri alization.XmlTy peAttribute(Ano nymousType=true , Namespace="urn: schemas-microsoft-com:office:spre adsheet")]
public partial class WorkbookWorkshe et
{
}

Adding the named tag ElementName="Wo rkbook" to the XmlRootAttribut e while not adding the ss namespace to the serializer generates

<?xml version="1.0" encoding="utf-8"?>
<Workbook xmlns:x="urn:sc hemas-microsoft-com:office:exce l" xmlns:html="htt p://www.w3.org/TR/REC-html40"
xmlns:c="urn:sc hemas-microsoft-com:office:comp onent" xmlns="urn:sche mas-microsoft-com:office:spre adsheet">
<Worksheet d2p1:Name="Shee t1" xmlns:d2p1="urn :schemas-microsoft-com:office:spre adsheet" xmlns="">

which suppresses the ss: prefix on the Workbook node, but still has the problem of the Worksheet node redefining xmlns.

Adding the Namespace= parameter to the XmlTypeAttribut e on WorkbookWorkshe et:

[System.CodeDom. Compiler.Genera tedCodeAttribut e("xsd", "2.0.50727. 42")]
[System.Serializ ableAttribute()]
[System.Componen tModel.Designer CategoryAttribu te("code")]
[System.Xml.Seri alization.XmlTy peAttribute(Ano nymousType = true, Namespace = "urn:schema s-microsoft-com:office:spre adsheet")]
public partial class WorkbookWorkshe et
{
}

generates

<?xml version="1.0" encoding="utf-8"?>
<Workbook xmlns:x="urn:sc hemas-microsoft-com:office:exce l" xmlns:html="htt p://www.w3.org/TR/REC-html40"
xmlns:c="urn:sc hemas-microsoft-com:office:comp onent" xmlns="urn:sche mas-microsoft-com:office:spre adsheet">
<Worksheet d2p1:Name="Shee t1" xmlns:d2p1="urn :schemas-microsoft-com:office:spre adsheet" xmlns="">

again with the redefinition of the default namespace on the Worksheet node.

The schema where Workbook and Worksheet are defined looks like this (some hopefully unrelated details left out for brevity):

<?xml version="1.0" encoding="utf-8"?>
<xs:schema xmlns:x="urn:sc hemas-microsoft-com:office:exce l" xmlns:html="htt p://www.w3.org/TR/REC-html40"
xmlns:ss="urn:s chemas-microsoft-com:office:spre adsheet" xmlns:o="urn:sc hemas-microsoft-com:office:offi ce"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:c="urn:sc hemas-microsoft-com:office:comp onent" attributeFormDe fault="unqualif ied"
targetNamespace ="urn:schema s-microsoft-com:office:spre adsheet" elementFormDefa ult="unqualifie d">
<xs:import namespace="urn: schemas-microsoft-com:office:offi ce" />
<xs:import namespace="urn: schemas-microsoft-com:office:exce l" />
<xs:import namespace="urn: schemas-microsoft-com:office:comp onent" />
<xs:element name="Workbook" >
<xs:complexType >
<xs:sequence>
<xs:element name="Styles">
</xs:element>
<xs:element maxOccurs="unbo unded" name="Worksheet ">
<xs:complexType >
<xs:sequence>
</xs:sequence>
<xs:attribute ref="ss:Name" use="required" />
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
....

I appreciate your help, and look forward to other suggestions.

- Mark

Mar 12 '07 #4
Wen Yuan,

Please see my reply to Martin. I tried your suggestions, but they don't solve the problem.

- Mark
Mar 12 '07 #5
Mark Olbert wrote:
The schema where Workbook and Worksheet are defined looks like this (some hopefully unrelated details left out for brevity):

<?xml version="1.0" encoding="utf-8"?>
<xs:schema xmlns:x="urn:sc hemas-microsoft-com:office:exce l" xmlns:html="htt p://www.w3.org/TR/REC-html40"
xmlns:ss="urn:s chemas-microsoft-com:office:spre adsheet" xmlns:o="urn:sc hemas-microsoft-com:office:offi ce"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:c="urn:sc hemas-microsoft-com:office:comp onent" attributeFormDe fault="unqualif ied"
targetNamespace ="urn:schema s-microsoft-com:office:spre adsheet" elementFormDefa ult="unqualifie d">
Why is elementFormDefa ult set to unqualified? The MS reference schema
for Office 2003 sets that to qualified.

--

Martin Honnen --- MVP XML
http://JavaScript.FAQTs.com/
Mar 12 '07 #6
Martin,

That schema was generated by having VS2005 generate a schema off of an Excel XP XML file. In the Excel XP XML file the element names
are unqualified (I just double-checked that).

I don't know why that would've changed between Excel XP and Excel 2003.

Interestingly, changing the element form to qualified solved the problem. The generated XML file now looks like:

<?xml version="1.0" encoding="utf-8"?>
<ss:Workbook xmlns:x="urn:sc hemas-microsoft-com:office:exce l" xmlns:html="htt p://www.w3.org/TR/REC-html40"
xmlns:c="urn:sc hemas-microsoft-com:office:comp onent" xmlns:ss="urn:s chemas-microsoft-com:office:spre adsheet">
<ss:Worksheet ss:Name="Sheet1 ">
<ss:Table>
<ss:Row ss:Index="1">
<ss:Cell ss:Index="1">
<ss:Data ss:Type="String ">Ralphie</ss:Data>
</ss:Cell>
</ss:Row>
<ss:Row ss:Index="4">
<ss:Cell ss:Index="4">
<ss:Data ss:Type="String ">Joanie</ss:Data>
</ss:Cell>
</ss:Row>
</ss:Table>
</ss:Worksheet>
</ss:Workbook>

which Excel 2007 (I just upgraded, so I no longer have Excel XP to test with) is happy to load as an Excel file.

So the problem's solved (at least for now). Thank you!

I double-checked the file I used to generate the schema to see if it would load in Excel 2007. It does, without a hitch. Here's what
it looks like (edited for brevity):

<?xml version="1.0"?>
<Workbook xmlns="urn:sche mas-microsoft-com:office:spre adsheet"
xmlns:o="urn:sc hemas-microsoft-com:office:offi ce"
xmlns:x="urn:sc hemas-microsoft-com:office:exce l"
xmlns:ss="urn:s chemas-microsoft-com:office:spre adsheet"
xmlns:html="htt p://www.w3.org/TR/REC-html40">
<Worksheet ss:Name="Sheet1 ">
<Table ss:ExpandedColu mnCount="4" ss:ExpandedRowC ount="6" x:FullColumns=" 1"
x:FullRows="1" ss:DefaultColum nWidth="60" ss:DefaultRowHe ight="15">
<Row ss:AutoFitHeigh t="0">
<Cell><Data ss:Type="Number ">1</Data></Cell>
</Row>
<Row ss:AutoFitHeigh t="0">
<Cell><Data ss:Type="Number ">2</Data></Cell>
</Row>
<Row ss:AutoFitHeigh t="0"/>
<Row ss:AutoFitHeigh t="0">
<Cell ss:Index="2"><D ata ss:Type="String ">a</Data></Cell>
</Row>
<Row ss:AutoFitHeigh t="0"/>
<Row ss:AutoFitHeigh t="0">
<Cell ss:Index="4"><D ata ss:Type="String ">c</Data></Cell>
</Row>
</Table>
</Worksheet>
</Workbook>

I still wish I understood >>why<< it was solved, though, and why Excel XP generated an XML file with unqualified element names. It
looks like, if the xmlns attribute is specified on the root node you don't need to qualify the element names, but if it isn't, you
have to. Since I haven't been able to find a way to get the xmlns attribute added to the root node when I generate a file, I have to
qualify the element names.

Then again, if I had a dollar for every XML/XSD/namespace issue I didn't understand, I'd be filthy rich.

- Mark

On Mon, 12 Mar 2007 18:31:26 +0100, Martin Honnen <ma*******@yaho o.dewrote:
>Mark Olbert wrote:
>The schema where Workbook and Worksheet are defined looks like this (some hopefully unrelated details left out for brevity):

<?xml version="1.0" encoding="utf-8"?>
<xs:schema xmlns:x="urn:sc hemas-microsoft-com:office:exce l" xmlns:html="htt p://www.w3.org/TR/REC-html40"
xmlns:ss="urn: schemas-microsoft-com:office:spre adsheet" xmlns:o="urn:sc hemas-microsoft-com:office:offi ce"
xmlns:xs="http ://www.w3.org/2001/XMLSchema" xmlns:c="urn:sc hemas-microsoft-com:office:comp onent" attributeFormDe fault="unqualif ied"
targetNamespac e="urn:schema s-microsoft-com:office:spre adsheet" elementFormDefa ult="unqualifie d">

Why is elementFormDefa ult set to unqualified? The MS reference schema
for Office 2003 sets that to qualified.
Mar 12 '07 #7
Mark Olbert wrote:
I double-checked the file I used to generate the schema to see if it would load in Excel 2007. It does, without a hitch. Here's what
it looks like (edited for brevity):

<?xml version="1.0"?>
<Workbook xmlns="urn:sche mas-microsoft-com:office:spre adsheet"
xmlns:o="urn:sc hemas-microsoft-com:office:offi ce"
xmlns:x="urn:sc hemas-microsoft-com:office:exce l"
xmlns:ss="urn:s chemas-microsoft-com:office:spre adsheet"
xmlns:html="htt p://www.w3.org/TR/REC-html40">
<Worksheet ss:Name="Sheet1 ">
You misunderstand what elementFormDefa ult="unqualifie d" means. In that
sample both elements, the Workbook element, and the Worksheet element,
are in the namespace urn:schemas-microsoft-com:office:spre adsheet and a
schema modelling that needs
targetNamespace ="urn:schema s-microsoft-com:office:spre adsheet"
and
elementFormDefa ult="qualified"
.. The schema you had with a
targetNamespace ="urn:schema s-microsoft-com:office:spre adsheet" but with
elementFormDefa ult="unqualifie d" describes a Workbook element in the
targetNamespace where child elements like Worksheet are in no namespace,
hence the xmlns="" you got on that element.

--

Martin Honnen --- MVP XML
http://JavaScript.FAQTs.com/
Mar 13 '07 #8
Hi Mark,

Additionally, XML namespaces is used to provide a simple method for
qualifying element and attribute names used in XML documents.

For example:
<Workbook xmlns="urn:sche mas-microsoft-com:office:spre adsheet"
xmlns:o="urn:sc hemas-microsoft-com:office:offi ce"
xmlns:x="urn:sc hemas-microsoft-com:office:exce l"
xmlns:ss="urn:s chemas-microsoft-com:office:spre adsheet"
xmlns:html="htt p://www.w3.org/TR/REC-html40">
<Worksheet ss:Name="Sheet1 ">

"urn:schema s-microsoft-com:office:spre adsheet' is the default namespace for
both <Workbookand <WorkSheeteleme nt.

But if you have many <WorkBookelemen ts with the different meaning in XML
document, then how do you distinguish these <WorkBookelemen ts?
Namespace can help you in this scenario.

< Workbook xmlns="namespac e1">
...< Worksheet >
......< Workbook xmlns="namespac e2">
.........
......</WorkBook>
...</ Worksheet >
</ Workbook>

You can distinguish the root <Workbookelemen t by namespace "namespace1 "
and node <Workbook\Works heet\Workbookby namespace "namespace2 ".

Hope this will help you understand namespace.

You can get more detailed information by the following document.
http://www.w3.org/TR/REC-xml-names/
[Namespaces in XML 1.0 (Second Edition)]

Have a great day,
Sincerley,
Wen Yuan

Mar 15 '07 #9
Hi Martin,

Just want to check whether you have met any further issue?
Please feel free to update here. I'm glad to assist you.

Have a great day,
Sincerely,
Wen Yuan

Mar 19 '07 #10

This thread has been closed and replies have been disabled. Please start a new discussion.

Similar topics

0
4209
by: C. M. Sperberg-McQueen | last post by:
wooks (wookiz@hotmail.com) wrote: > <?xml version='1.0'?> > <userlogin xmlns="urn:faster:userlogin" > xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'> > <login>mick</login> > <password>brown</password> > </userlogin> > Above is my schema instance.
4
2446
by: Erik Moore | last post by:
I am both producing and parsing an xml document that needs to be validated against a schema. I wanted some consumers of the document to have the option of not performing a validation, so I left the nodes in the instance unqualified. An example of the document is below: <?xml version="1.0" encoding="utf-8" ?> <filingreceipt...
0
3009
by: keith bannister via .NET 247 | last post by:
(Type your message here) -------------------------------- From: keith bannister Hi, I'm new to .net (as of last week) but here goes. I want to serialize/deserialize a file the conforms to an XML schema (xsd).
5
7272
by: Keith Bannister | last post by:
I'm new to .net so here goes. I'm tying to deserialize a class that is associated with an XML schema. I created the C# class with xsd.exe as below: xsd.exe /c /n:somenamespace properties.xsd this creates properties.cs
4
2718
by: Wayne Wengert | last post by:
I am still stuck trying to create a Class to use for exporting and importing array data to/from XML. The format of the XML that I want to import/export is shown below as is the Class and the code I am using to create a sample XML file. I am trying to dimension the ArrayOfJudgeEntity to have two sets of the JudgeTableEntity values. When I run...
1
2071
by: Ivo Bronsveld | last post by:
All, I have quite a challenging task ahead of me. I need to write an object model (for code access) based on a schema, which cannot be made into a dataset because of it's complexity. So I created a couple of objects and serializing it into XML based upon the schema works perfectly. The XML / Schema looks something like this:
2
2503
by: farseer | last post by:
Hi, First, sorry for this long post, but i'd like to explain my problem in detail... i have generated some classes from my schema. Classes are generated for the root (overall document), complexTypes with complexContents (this is how my types in the xsd are defined), and elements defined as complextypes that contain more than one unbounded...
16
3502
by: TT (Tom Tempelaere) | last post by:
Hi all, I created an XSD to define the structure of an XML file for my project. I made an XML file linked to the XSD using XmlSpy. The problem is that if I read the file using .NET XmlDocument and then query for the root element, the result is always null (1). However if I strip the root element of all attributes generated by XmlSpy, then...
4
4800
by: BorisBoshond | last post by:
Hi all, Hope someone is able and willing to help me with following problem. I received a xsd file from another company, our company i supposed to return xml based on that xsd. Problem is that I don't really understand how these namespace work in xml. (I am however aware of what problems namespaces solve) I'm not even sure if the provided...
0
7347
by: Hystou | last post by:
Most computers default to English, but sometimes we require a different language, especially when relocating. Forgot to request a specific language before your computer shipped? No problem! You can effortlessly switch the default language on Windows 10 without reinstalling. I'll walk you through it. First, let's disable language...
0
7590
Oralloy
by: Oralloy | last post by:
Hello folks, I am unable to find appropriate documentation on the type promotion of bit-fields when using the generalised comparison operator "<=>". The problem is that using the GNU compilers, it seems that the internal comparison operator "<=>" tries to promote arguments from unsigned to signed. This is as boiled down as I can make it. ...
0
7733
jinu1996
by: jinu1996 | last post by:
In today's digital age, having a compelling online presence is paramount for businesses aiming to thrive in a competitive landscape. At the heart of this digital strategy lies an intricately woven tapestry of website design and digital marketing. It's not merely about having a website; it's about crafting an immersive digital experience that...
1
7344
by: Hystou | last post by:
Overview: Windows 11 and 10 have less user interface control over operating system update behaviour than previous versions of Windows. In Windows 11 and 10, there is no way to turn off the Windows Update option using the Control Panel or Settings app; it automatically checks for updates and installs any it finds, whether you like it or not. For...
0
7684
tracyyun
by: tracyyun | last post by:
Dear forum friends, With the development of smart home technology, a variety of wireless communication protocols have appeared on the market, such as Zigbee, Z-Wave, Wi-Fi, Bluetooth, etc. Each protocol has its own unique characteristics and advantages, but as a user who is planning to build a smart home system, I am a bit confused by the...
0
5883
agi2029
by: agi2029 | last post by:
Let's talk about the concept of autonomous AI software engineers and no-code agents. These AIs are designed to manage the entire lifecycle of a software development project—planning, coding, testing, and deployment—without human intervention. Imagine an AI that can take a project description, break it down, write the code, debug it, and then...
1
5264
isladogs
by: isladogs | last post by:
The next Access Europe User Group meeting will be on Wednesday 1 May 2024 starting at 18:00 UK time (6PM UTC+1) and finishing by 19:30 (7.30PM). In this session, we are pleased to welcome a new presenter, Adolph Dupré who will be discussing some powerful techniques for using class modules. He will explain when you may want to use classes...
0
3391
by: adsilva | last post by:
A Windows Forms form does not have the event Unload, like VB6. What one acts like?
1
963
muto222
by: muto222 | last post by:
How can i add a mobile payment intergratation into php mysql website.

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.