473,544 Members | 1,760 Online
Bytes | Software Development & Data Engineering Community
+ Post

Home Posts Topics Members FAQ

vs2003 & xsd:extension

Hello,

I have already read several existing posts about xsd:extension, but do not
find something useful to my test case. I have one xml file and one xsd file.
I can use a simple command line (C#) program to validate the xml file against
the xsd file without any error. The problem is that when I validate the same
xml file within VisualStudio 2003, I got five errors, which are all related
to xsd:extension. It seems that those "problem" attributes and elements are
not inherited in the derived type. Here is one of the famous error:

Could not find any attribute 'routingNum' of element 'hat'.

Any input is appreciated much. Thanks.

The following are the xml file and the xsd:

<!--Definitive XML Schema by Priscilla Walmsley (c) 2001 Prentice Hall PTR -->
<c:items xmlns:xsi="http ://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocat ion="http://chapter14.xsd
http://localhost/xsd/chapter14.xsd"
xmlns:c="http://chapter14.xsd">
<hat routingNum="123 456" effDate="2002-04-02" lang="en-US">
<number>557</number>
<name>Ten-Gallon Hat</name>
<description>Th is is a great hat!</description>
</hat>
<umbrella routingNum="123 " effDate="2002-04-02">
<number>557</number>
<name>Ten-Gallon Hat</name>
</umbrella>
<shirt routingNum="124 " effDate="2002-04-02" sleeve="17">
<number>557</number>
<name>Short-Sleeved Linen Blouse</name>
<color value="blue"/>
<size system="US-DRESS">6</size>
</shirt>
</c:items>

---------------------------------------------------
<!--Definitive XML Schema by Priscilla Walmsley (c) 2001 Prentice Hall PTR -->
<xsd:schema xmlns:xsd="http ://www.w3.org/2001/XMLSchema"
targetNamespace ="http://chapter14.xsd"
xmlns="http://chapter14.xsd">

<xsd:annotation >
<xsd:documentat ion>
This example illustrates complex types that are derived from other
specified types.
</xsd:documentati on>
</xsd:annotation>

<xsd:element name="items" type="ItemsType "/>

<xsd:complexTyp e name="ItemsType ">
<xsd:choice minOccurs="0" maxOccurs="unbo unded">
<xsd:element name="hat" type="ProductTy pe"/>
<xsd:element name="umbrella" type="Restricte dProductType"/>
<xsd:element name="shirt" type="ShirtType "/>
</xsd:choice>
</xsd:complexType >

<!--Empty Content Type-->
<xsd:complexTyp e name="ItemType" abstract="true" >
<xsd:attribut e name="routingNu m" type="xsd:integ er"/>
</xsd:complexType >

<!--Empty Content Extension (with Attribute Extension)-->
<xsd:complexTyp e name="ProductTy pe">
<xsd:complexCon tent>
<xsd:extensio n base="ItemType" >
<xsd:sequence >
<xsd:element name="number" type="xsd:integ er"/>
<xsd:element name="name" type="xsd:strin g"/>
<xsd:element name="descripti on" type="xsd:strin g" minOccurs="0"/>
</xsd:sequence>
<xsd:attribut e name="effDate" type="xsd:date"/>
<xsd:attribut e name="lang" type="xsd:langu age"/>
</xsd:extension>
</xsd:complexCont ent>
</xsd:complexType >

<!--Complex Content Restriction-->
<xsd:complexTyp e name="Restricte dProductType">
<xsd:complexCon tent>
<xsd:restrictio n base="ProductTy pe">
<xsd:sequence >
<xsd:element name="number" type="xsd:integ er"/>
<xsd:element name="name" type="xsd:token "/>
</xsd:sequence>
<xsd:attribut e name="routingNu m" type="xsd:short " use="required"/>
<xsd:attribut e name="effDate" type="xsd:date" default="1900-01-01"/>
<xsd:attribut e name="lang" use="prohibited "/>
</xsd:restriction >
</xsd:complexCont ent>
</xsd:complexType >

<!--Complex Content Extension-->
<xsd:complexTyp e name="ShirtType ">
<xsd:complexCon tent>
<xsd:extensio n base="Restricte dProductType">
<xsd:choice maxOccurs="unbo unded">
<xsd:element name="size" type="SmallSize Type"/>
<xsd:element name="color" type="ColorType "/>
</xsd:choice>
<xsd:attribut e name="sleeve" type="xsd:integ er"/>
</xsd:extension>
</xsd:complexCont ent>
</xsd:complexType >

<!--Simple Content Extension-->
<xsd:complexTyp e name="SizeType" >
<xsd:simpleCont ent>
<xsd:extensio n base="xsd:integ er">
<xsd:attribut e name="system" type="xsd:token "/>
</xsd:extension>
</xsd:simpleConte nt>
</xsd:complexType >

<!--Simple Content Restriction-->
<xsd:complexTyp e name="SmallSize Type">
<xsd:simpleCont ent>
<xsd:restrictio n base="SizeType" >
<xsd:minInclusi ve value="2"/>
<xsd:maxInclusi ve value="6"/>
<xsd:attribut e name="system" type="xsd:token "
use="required"/>
</xsd:restriction >
</xsd:simpleConte nt>
</xsd:complexType >

<xsd:complexTyp e name="ColorType ">
<xsd:attribut e name="value" type="xsd:strin g"/>
</xsd:complexType >

</xsd:schema>

Nov 12 '05 #1
3 2044
Your xml and xsd validate fine with the validation engine in VS 2003. Are
you putting your schema file in the right location?

"man-in-nature" <ma*********@di scussions.micro soft.com> wrote in message
news:DA******** *************** ***********@mic rosoft.com...
Hello,

I have already read several existing posts about xsd:extension, but do not
find something useful to my test case. I have one xml file and one xsd file. I can use a simple command line (C#) program to validate the xml file against the xsd file without any error. The problem is that when I validate the same xml file within VisualStudio 2003, I got five errors, which are all related to xsd:extension. It seems that those "problem" attributes and elements are not inherited in the derived type. Here is one of the famous error:

Could not find any attribute 'routingNum' of element 'hat'.

Any input is appreciated much. Thanks.

The following are the xml file and the xsd:

<!--Definitive XML Schema by Priscilla Walmsley (c) 2001 Prentice Hall PTR --> <c:items xmlns:xsi="http ://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocat ion="http://chapter14.xsd
http://localhost/xsd/chapter14.xsd"
xmlns:c="http://chapter14.xsd">
<hat routingNum="123 456" effDate="2002-04-02" lang="en-US">
<number>557</number>
<name>Ten-Gallon Hat</name>
<description>Th is is a great hat!</description>
</hat>
<umbrella routingNum="123 " effDate="2002-04-02">
<number>557</number>
<name>Ten-Gallon Hat</name>
</umbrella>
<shirt routingNum="124 " effDate="2002-04-02" sleeve="17">
<number>557</number>
<name>Short-Sleeved Linen Blouse</name>
<color value="blue"/>
<size system="US-DRESS">6</size>
</shirt>
</c:items>

---------------------------------------------------
<!--Definitive XML Schema by Priscilla Walmsley (c) 2001 Prentice Hall PTR --> <xsd:schema xmlns:xsd="http ://www.w3.org/2001/XMLSchema"
targetNamespace ="http://chapter14.xsd"
xmlns="http://chapter14.xsd">

<xsd:annotation >
<xsd:documentat ion>
This example illustrates complex types that are derived from other
specified types.
</xsd:documentati on>
</xsd:annotation>

<xsd:element name="items" type="ItemsType "/>

<xsd:complexTyp e name="ItemsType ">
<xsd:choice minOccurs="0" maxOccurs="unbo unded">
<xsd:element name="hat" type="ProductTy pe"/>
<xsd:element name="umbrella" type="Restricte dProductType"/>
<xsd:element name="shirt" type="ShirtType "/>
</xsd:choice>
</xsd:complexType >

<!--Empty Content Type-->
<xsd:complexTyp e name="ItemType" abstract="true" >
<xsd:attribut e name="routingNu m" type="xsd:integ er"/>
</xsd:complexType >

<!--Empty Content Extension (with Attribute Extension)-->
<xsd:complexTyp e name="ProductTy pe">
<xsd:complexCon tent>
<xsd:extensio n base="ItemType" >
<xsd:sequence >
<xsd:element name="number" type="xsd:integ er"/>
<xsd:element name="name" type="xsd:strin g"/>
<xsd:element name="descripti on" type="xsd:strin g" minOccurs="0"/> </xsd:sequence>
<xsd:attribut e name="effDate" type="xsd:date"/>
<xsd:attribut e name="lang" type="xsd:langu age"/>
</xsd:extension>
</xsd:complexCont ent>
</xsd:complexType >

<!--Complex Content Restriction-->
<xsd:complexTyp e name="Restricte dProductType">
<xsd:complexCon tent>
<xsd:restrictio n base="ProductTy pe">
<xsd:sequence >
<xsd:element name="number" type="xsd:integ er"/>
<xsd:element name="name" type="xsd:token "/>
</xsd:sequence>
<xsd:attribut e name="routingNu m" type="xsd:short " use="required"/>
<xsd:attribut e name="effDate" type="xsd:date" default="1900-01-01"/> <xsd:attribut e name="lang" use="prohibited "/>
</xsd:restriction >
</xsd:complexCont ent>
</xsd:complexType >

<!--Complex Content Extension-->
<xsd:complexTyp e name="ShirtType ">
<xsd:complexCon tent>
<xsd:extensio n base="Restricte dProductType">
<xsd:choice maxOccurs="unbo unded">
<xsd:element name="size" type="SmallSize Type"/>
<xsd:element name="color" type="ColorType "/>
</xsd:choice>
<xsd:attribut e name="sleeve" type="xsd:integ er"/>
</xsd:extension>
</xsd:complexCont ent>
</xsd:complexType >

<!--Simple Content Extension-->
<xsd:complexTyp e name="SizeType" >
<xsd:simpleCont ent>
<xsd:extensio n base="xsd:integ er">
<xsd:attribut e name="system" type="xsd:token "/>
</xsd:extension>
</xsd:simpleConte nt>
</xsd:complexType >

<!--Simple Content Restriction-->
<xsd:complexTyp e name="SmallSize Type">
<xsd:simpleCont ent>
<xsd:restrictio n base="SizeType" >
<xsd:minInclusi ve value="2"/>
<xsd:maxInclusi ve value="6"/>
<xsd:attribut e name="system" type="xsd:token "
use="required"/>
</xsd:restriction >
</xsd:simpleConte nt>
</xsd:complexType >

<xsd:complexTyp e name="ColorType ">
<xsd:attribut e name="value" type="xsd:strin g"/>
</xsd:complexType >

</xsd:schema>

Nov 12 '05 #2
I'm having the same problem with attributes from base types showing up
properly in the derived type in VS.NET 2003. VS understands the rest of the
schema, so it's finding the schema. It just doesn't seem to recognize
attributes from the base type of an xs:extension'ed type.
"man-in-nature" <ma*********@di scussions.micro soft.com> wrote in message
news:DA******** *************** ***********@mic rosoft.com...
Hello,

I have already read several existing posts about xsd:extension, but do not
find something useful to my test case. I have one xml file and one xsd file. I can use a simple command line (C#) program to validate the xml file against the xsd file without any error. The problem is that when I validate the same xml file within VisualStudio 2003, I got five errors, which are all related to xsd:extension. It seems that those "problem" attributes and elements are not inherited in the derived type. Here is one of the famous error:

Could not find any attribute 'routingNum' of element 'hat'.

Any input is appreciated much. Thanks.

The following are the xml file and the xsd:

<!--Definitive XML Schema by Priscilla Walmsley (c) 2001 Prentice Hall PTR --> <c:items xmlns:xsi="http ://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocat ion="http://chapter14.xsd
http://localhost/xsd/chapter14.xsd"
xmlns:c="http://chapter14.xsd">
<hat routingNum="123 456" effDate="2002-04-02" lang="en-US">
<number>557</number>
<name>Ten-Gallon Hat</name>
<description>Th is is a great hat!</description>
</hat>
<umbrella routingNum="123 " effDate="2002-04-02">
<number>557</number>
<name>Ten-Gallon Hat</name>
</umbrella>
<shirt routingNum="124 " effDate="2002-04-02" sleeve="17">
<number>557</number>
<name>Short-Sleeved Linen Blouse</name>
<color value="blue"/>
<size system="US-DRESS">6</size>
</shirt>
</c:items>

---------------------------------------------------
<!--Definitive XML Schema by Priscilla Walmsley (c) 2001 Prentice Hall PTR --> <xsd:schema xmlns:xsd="http ://www.w3.org/2001/XMLSchema"
targetNamespace ="http://chapter14.xsd"
xmlns="http://chapter14.xsd">

<xsd:annotation >
<xsd:documentat ion>
This example illustrates complex types that are derived from other
specified types.
</xsd:documentati on>
</xsd:annotation>

<xsd:element name="items" type="ItemsType "/>

<xsd:complexTyp e name="ItemsType ">
<xsd:choice minOccurs="0" maxOccurs="unbo unded">
<xsd:element name="hat" type="ProductTy pe"/>
<xsd:element name="umbrella" type="Restricte dProductType"/>
<xsd:element name="shirt" type="ShirtType "/>
</xsd:choice>
</xsd:complexType >

<!--Empty Content Type-->
<xsd:complexTyp e name="ItemType" abstract="true" >
<xsd:attribut e name="routingNu m" type="xsd:integ er"/>
</xsd:complexType >

<!--Empty Content Extension (with Attribute Extension)-->
<xsd:complexTyp e name="ProductTy pe">
<xsd:complexCon tent>
<xsd:extensio n base="ItemType" >
<xsd:sequence >
<xsd:element name="number" type="xsd:integ er"/>
<xsd:element name="name" type="xsd:strin g"/>
<xsd:element name="descripti on" type="xsd:strin g" minOccurs="0"/> </xsd:sequence>
<xsd:attribut e name="effDate" type="xsd:date"/>
<xsd:attribut e name="lang" type="xsd:langu age"/>
</xsd:extension>
</xsd:complexCont ent>
</xsd:complexType >

<!--Complex Content Restriction-->
<xsd:complexTyp e name="Restricte dProductType">
<xsd:complexCon tent>
<xsd:restrictio n base="ProductTy pe">
<xsd:sequence >
<xsd:element name="number" type="xsd:integ er"/>
<xsd:element name="name" type="xsd:token "/>
</xsd:sequence>
<xsd:attribut e name="routingNu m" type="xsd:short " use="required"/>
<xsd:attribut e name="effDate" type="xsd:date" default="1900-01-01"/> <xsd:attribut e name="lang" use="prohibited "/>
</xsd:restriction >
</xsd:complexCont ent>
</xsd:complexType >

<!--Complex Content Extension-->
<xsd:complexTyp e name="ShirtType ">
<xsd:complexCon tent>
<xsd:extensio n base="Restricte dProductType">
<xsd:choice maxOccurs="unbo unded">
<xsd:element name="size" type="SmallSize Type"/>
<xsd:element name="color" type="ColorType "/>
</xsd:choice>
<xsd:attribut e name="sleeve" type="xsd:integ er"/>
</xsd:extension>
</xsd:complexCont ent>
</xsd:complexType >

<!--Simple Content Extension-->
<xsd:complexTyp e name="SizeType" >
<xsd:simpleCont ent>
<xsd:extensio n base="xsd:integ er">
<xsd:attribut e name="system" type="xsd:token "/>
</xsd:extension>
</xsd:simpleConte nt>
</xsd:complexType >

<!--Simple Content Restriction-->
<xsd:complexTyp e name="SmallSize Type">
<xsd:simpleCont ent>
<xsd:restrictio n base="SizeType" >
<xsd:minInclusi ve value="2"/>
<xsd:maxInclusi ve value="6"/>
<xsd:attribut e name="system" type="xsd:token "
use="required"/>
</xsd:restriction >
</xsd:simpleConte nt>
</xsd:complexType >

<xsd:complexTyp e name="ColorType ">
<xsd:attribut e name="value" type="xsd:strin g"/>
</xsd:complexType >

</xsd:schema>

Nov 12 '05 #3
Yes, VS2003 can find the schema in question. It never complains that "Visual
Studio could not locate a schema for this document...". It is easy to verify
this by changing the target name space in the instance document
("xmlns:c="http ://chanpter14.xsd" ) to something else.

Regards

"Zafar Abbas [MSFT]" wrote:
Your xml and xsd validate fine with the validation engine in VS 2003. Are
you putting your schema file in the right location?

"man-in-nature" <ma*********@di scussions.micro soft.com> wrote in message
news:DA******** *************** ***********@mic rosoft.com...
Hello,

I have already read several existing posts about xsd:extension, but do not
find something useful to my test case. I have one xml file and one xsd

file.
I can use a simple command line (C#) program to validate the xml file

against
the xsd file without any error. The problem is that when I validate the

same
xml file within VisualStudio 2003, I got five errors, which are all

related
to xsd:extension. It seems that those "problem" attributes and elements

are
not inherited in the derived type. Here is one of the famous error:

Could not find any attribute 'routingNum' of element 'hat'.

Any input is appreciated much. Thanks.

The following are the xml file and the xsd:

<!--Definitive XML Schema by Priscilla Walmsley (c) 2001 Prentice Hall

PTR -->
<c:items xmlns:xsi="http ://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocat ion="http://chapter14.xsd
http://localhost/xsd/chapter14.xsd"
xmlns:c="http://chapter14.xsd">
<hat routingNum="123 456" effDate="2002-04-02" lang="en-US">
<number>557</number>
<name>Ten-Gallon Hat</name>
<description>Th is is a great hat!</description>
</hat>
<umbrella routingNum="123 " effDate="2002-04-02">
<number>557</number>
<name>Ten-Gallon Hat</name>
</umbrella>
<shirt routingNum="124 " effDate="2002-04-02" sleeve="17">
<number>557</number>
<name>Short-Sleeved Linen Blouse</name>
<color value="blue"/>
<size system="US-DRESS">6</size>
</shirt>
</c:items>

---------------------------------------------------
<!--Definitive XML Schema by Priscilla Walmsley (c) 2001 Prentice Hall

PTR -->
<xsd:schema xmlns:xsd="http ://www.w3.org/2001/XMLSchema"
targetNamespace ="http://chapter14.xsd"
xmlns="http://chapter14.xsd">

<xsd:annotation >
<xsd:documentat ion>
This example illustrates complex types that are derived from other
specified types.
</xsd:documentati on>
</xsd:annotation>

<xsd:element name="items" type="ItemsType "/>

<xsd:complexTyp e name="ItemsType ">
<xsd:choice minOccurs="0" maxOccurs="unbo unded">
<xsd:element name="hat" type="ProductTy pe"/>
<xsd:element name="umbrella" type="Restricte dProductType"/>
<xsd:element name="shirt" type="ShirtType "/>
</xsd:choice>
</xsd:complexType >

<!--Empty Content Type-->
<xsd:complexTyp e name="ItemType" abstract="true" >
<xsd:attribut e name="routingNu m" type="xsd:integ er"/>
</xsd:complexType >

<!--Empty Content Extension (with Attribute Extension)-->
<xsd:complexTyp e name="ProductTy pe">
<xsd:complexCon tent>
<xsd:extensio n base="ItemType" >
<xsd:sequence >
<xsd:element name="number" type="xsd:integ er"/>
<xsd:element name="name" type="xsd:strin g"/>
<xsd:element name="descripti on" type="xsd:strin g"

minOccurs="0"/>
</xsd:sequence>
<xsd:attribut e name="effDate" type="xsd:date"/>
<xsd:attribut e name="lang" type="xsd:langu age"/>
</xsd:extension>
</xsd:complexCont ent>
</xsd:complexType >

<!--Complex Content Restriction-->
<xsd:complexTyp e name="Restricte dProductType">
<xsd:complexCon tent>
<xsd:restrictio n base="ProductTy pe">
<xsd:sequence >
<xsd:element name="number" type="xsd:integ er"/>
<xsd:element name="name" type="xsd:token "/>
</xsd:sequence>
<xsd:attribut e name="routingNu m" type="xsd:short " use="required"/>
<xsd:attribut e name="effDate" type="xsd:date"

default="1900-01-01"/>
<xsd:attribut e name="lang" use="prohibited "/>
</xsd:restriction >
</xsd:complexCont ent>
</xsd:complexType >

<!--Complex Content Extension-->
<xsd:complexTyp e name="ShirtType ">
<xsd:complexCon tent>
<xsd:extensio n base="Restricte dProductType">
<xsd:choice maxOccurs="unbo unded">
<xsd:element name="size" type="SmallSize Type"/>
<xsd:element name="color" type="ColorType "/>
</xsd:choice>
<xsd:attribut e name="sleeve" type="xsd:integ er"/>
</xsd:extension>
</xsd:complexCont ent>
</xsd:complexType >

<!--Simple Content Extension-->
<xsd:complexTyp e name="SizeType" >
<xsd:simpleCont ent>
<xsd:extensio n base="xsd:integ er">
<xsd:attribut e name="system" type="xsd:token "/>
</xsd:extension>
</xsd:simpleConte nt>
</xsd:complexType >

<!--Simple Content Restriction-->
<xsd:complexTyp e name="SmallSize Type">
<xsd:simpleCont ent>
<xsd:restrictio n base="SizeType" >
<xsd:minInclusi ve value="2"/>
<xsd:maxInclusi ve value="6"/>
<xsd:attribut e name="system" type="xsd:token "
use="required"/>
</xsd:restriction >
</xsd:simpleConte nt>
</xsd:complexType >

<xsd:complexTyp e name="ColorType ">
<xsd:attribut e name="value" type="xsd:strin g"/>
</xsd:complexType >

</xsd:schema>


Nov 12 '05 #4

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

Similar topics

2
3080
by: Sean Bright | last post by:
Hi there. I'm having a problem which I hope is a simple one... Any help would be appreciated. I think it has something to do with the way attributes are (or are not) inherited in schemas... This is the content of my XML Schema (minus the schema tag): <xsd:complexType name="AType"> <xsd:attribute name="attr1" type="xsd:string" />
1
2090
by: mre | last post by:
Is there a program that will flatten an XSD, that is, will transform... <xsd:element name="name" type="nameType"/> <xsd:complexType name="nameType"> <xsd:sequence> <xsd:element name="firstname" type="xsd:string"/> <xsd:element name="surname" type="xsd:string"/> </xsd:sequence> </xsd:complexType>
4
1666
by: trexim | last post by:
It seems that .NET does not support xsd:extension and xsd:attribute. What is the alternative? Thanks,
8
6503
by: aevans1108 | last post by:
Greetings I can't seem to inherit enumerated values from a globally defined type in my XML schema. XmlSchema.Compile() doesn't like it. Here's the schema. <?xml version="1.0" encoding="UTF-8" ?> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified">
4
2014
by: Mike Jansen | last post by:
Does anyone know why if I create a complexType based off another complexType using xsd:extension the attributes don't seem to be inherited? Is this a bug/non-implementation in the .NET Schema editor and the XML validator? Thanks, Mike Jansen
3
2018
by: comic_rage | last post by:
I am trying to get my schema to look like this <xsd:extension base="MyExtension"> <xsd:attributeGroup ref="DocumentAttributes"> <xsd:annotation> <xsd:documentation>Notes</xsd:documentation> </xsd:annotation> </xsd:attributeGroup> </xsd:extension>
3
1738
by: Amol | last post by:
Hi all, I have a case where I have a element that can appear under multiple elements e.g. <AppFunctions> <UseTemplate name="1"/> <MethodSet name="2"> <UseTemplate name="3" /> <MethodCall name="4" /> </MethodSet>
5
1780
by: Kunal | last post by:
I'm unable to use the "xsd:all" tag in derived objects, in a hierarchical schema setup. For example, I have the following schema (that doesn't validate with XMLSpy): (UserOfDerived extends Derived extends Base) <!-- Base.xsd --> .... <xsd:complexType name = "Base" abstract = "true"> <attribute name = "revision" type = "xsd:string"/>
4
2597
by: Dmitry Kulinich | last post by:
Guys! Is there are any possibility to create nodes with duplicate names and different types in XSD? I've read the whole specification and tried in a many different ways, but not successfull. -- Thank you for any help, Dmitry Kulinich, Ukrain,
0
7414
marktang
by: marktang | last post by:
ONU (Optical Network Unit) is one of the key components for providing high-speed Internet services. Its primary function is to act as an endpoint device located at the user's premises. However, people are often confused as to whether an ONU can Work As a Router. In this blog post, we’ll explore What is ONU, What Is Router, ONU & Router’s main...
0
7757
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
7360
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
7699
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
5895
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...
0
3400
by: TSSRALBI | last post by:
Hello I'm a network technician in training and I need your help. I am currently learning how to create and manage the different types of VPNs and I have a question about LAN-to-LAN VPNs. The last exercise I practiced was to create a LAN-to-LAN VPN between two Pfsense firewalls, by using IPSEC protocols. I succeeded, with both firewalls in...
1
1833
by: 6302768590 | last post by:
Hai team i want code for transfer the data from one system to another through IP address by using C# our system has to for every 5mins then we have to update the data what the data is updated we have to send another system
1
982
muto222
by: muto222 | last post by:
How can i add a mobile payment intergratation into php mysql website.
0
651
bsmnconsultancy
by: bsmnconsultancy | last post by:
In today's digital era, a well-designed website is crucial for businesses looking to succeed. Whether you're a small business owner or a large corporation in Toronto, having a strong online presence can significantly impact your brand's success. BSMN Consultancy, a leader in Website Development in Toronto offers valuable insights into creating...

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.