 |
|
|
This is a multi-part message in MIME format.
------=_NextPart_000_00F7_01C45F01.90FA5F30
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Announcing: New XML Editor in Visual Studio 2005 Beta 1
Visual Studio 2005 Beta 1 contains a completely new XML Editor, built on =
top of the core text editor provided by Visual Studio. It is entirely =
written in C# and leverages all the cool stuff provided by the =
System.Xml .NET assembly. The new XML editor provides support for =
editing XML and DTD content, including special support for XSD and XSL. =
It contains the following handy features:
a.. Full syntax coloring for all XML and DTD syntax.=20
b.. Well formedness checking while you type, with red squiggles and =
error list.=20
c.. Intellisense based on any DTD, XDR and XSD schemas.=20
d.. Validation-while-you-type with blue squiggles and error list.=20
e.. Auto-completion of namespace declarations, end tags and attribute =
value quotes.=20
f.. Support for xsi:schemaLocation and xsi:noNamespaceSchemaLocation =
attributes.=20
g.. Schema picker dialog for overriding schemas used for validation, =
which is then remembered as a document property in your solution.=20
h.. Schema cache for commonly used schemas with standard set provided =
out of the box. You can easily add your own schemas here or edit the =
existing ones to constantly improve your XML editing experience.=20
i.. Smart Formatter that is more than a pretty printer. It honors and =
formatting of attributes that you may have done by hand and it fixes up =
the most common mistakes people make in XML, like unquoted attribute =
values.=20
j.. Smart indenting based on XML element depth.=20
k.. Inline expand/collapse support.=20
l.. Easy navigation between start and end tags using brace matching =
command (Ctrl+]) .=20
m.. Brace highlighting so you see which tags are being closed as you =
type.=20
n.. Goto Definition command for navigating between elements and their =
associated DTD, XDR or XSD schema definitions. This command can also =
navigate from an entity reference to the entity definition in the DTD.=20
o.. Tool tips that popup showing xsd:annotations for the element or =
attribute under the mouse.=20
p.. XSL and XSD compilation errors while you type, providing even more =
error checking that can be represented in the schemas alone.=20
q.. Show XSLT Output command available on any XML or XSLT file.
XSD Schema Inference
The editor provides a handy command named "Create Schema" which does one =
of three things:
1.. Convert associated DTD to XSD=20
2.. Convert associated XDR schema to XSD=20
3.. Infer a schema from the XML
This is by far the easiest way to get started with designing an XSD =
schema.
XSLT Debugging
In non-Express SKU's only, this feature gives you a powerful XSLT =
debugger, fully integrated into the overall Visual Studio debugging =
experience so you can step from C# code directly into the XSLT transform =
itself and back out, or from XSLT out to extension objects and back. It =
also provides a "Debug XSL" command on XML editor toolbar to start =
debugging directly from XML or XSL file.
Once debugging has started the standard Visual Studio debugging menu is =
available including special support for the following:
=B7 Setting and clearing breakpoints, at the node level (as =
opposed to line level).
=B7 Locals window that shows XSLT variables and parameters that =
are in scope.
=B7 Call Stack window that shows XSLT template stack.
Deep VS Integration & Extensibility
All the advanced core text editor commands and configurability is =
available, for example:
a.. Fully configurable colors using standard =
Tools/Options/Environment/Fonts and Colors property page.=20
b.. Fully integrated text editor settings (Tools/Options/Text =
Editor/XML) for general, tabs and miscellaneous settings.=20
c.. Support for the new Visual Studio 2005 "Import/Export Settings" =
feature.
Support for multiple-views over the same buffer. In Visual Studio 2003, =
the XSD designer and grid views were only available from a tab at the =
bottom of the document window, which means you could not view both ways =
at the same time. This limitation has been removed, and each different =
view is now a full fledged document window. =20
Custom XML designers can also be registered per file extension and/or =
XML namespace URI, which is how the Visual Studio XSD designer, DataSet =
designer, and the Grid View are associated with the XML editor. Anyone =
can now register an XML designer for a given namespace and the XML =
editor will automatically provide a View Designer menu item for invoking =
that designer. In fact if you are planning a custom XML designer, I'd =
love to chat about integration with this new XML text editor.
All feedback is welcome!
XML Editor team,
Microsoft.
=20
------=_NextPart_000_00F7_01C45F01.90FA5F30
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY><FONT face=3DArial size=3D2></FONT>
<H2 style=3D"MARGIN: 12pt 0in 3pt"><SPAN style=3D"FONT-SIZE: 12pt"><FONT =
face=3DArial><FONT size=3D2>Announcing: New XML Editor in Visual Studio =
2005 Beta=20
1<?xml:namespace prefix =3D o ns =3D =
"urn:schemas-microsoft-com:office:office"=20
/><o:p></o:p></FONT></FONT></SPAN></H2>
<P><A href=3D"http://lab.msdn.microsoft.com/vs2005/"><FONT face=3DArial=20
size=3D2>Visual Studio 2005 Beta 1 </FONT></A><FONT face=3DArial><FONT=20
size=3D2>contains a completely new XML Editor, built on top of the core =
text=20
editor provided by Visual Studio. It is entirely written in C# and =
leverages all the cool stuff provided by the System.Xml .NET =
assembly. The=20
new XML editor provides support for editing XML and DTD content, =
including=20
special support for XSD and XSL. It contains the following =
handy=20
features:<o:p></o:p></FONT></FONT></P>
<UL type=3Ddisc>
<LI class=3DMsoNormal=20
style=3D"MARGIN: 0in 0in 0pt; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto; mso-list: l0 level1 lfo1; tab-stops: list =
.5in"><FONT=20
face=3DArial size=3D2>Full syntax coloring for all XML and DTD =
syntax.<o:p></o:p>=20
</FONT>
<LI class=3DMsoNormal=20
style=3D"MARGIN: 0in 0in 0pt; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto; mso-list: l0 level1 lfo1; tab-stops: list =
.5in"><FONT=20
face=3DArial size=3D2>Well formedness checking while you type, with =
red squiggles=20
and error list.<o:p></o:p> </FONT>
<LI class=3DMsoNormal=20
style=3D"MARGIN: 0in 0in 0pt; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto; mso-list: l0 level1 lfo1; tab-stops: list =
.5in"><FONT=20
face=3DArial size=3D2>Intellisense based on any DTD, XDR and XSD=20
schemas.<o:p></o:p> </FONT>
<LI class=3DMsoNormal=20
style=3D"MARGIN: 0in 0in 0pt; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto; mso-list: l0 level1 lfo1; tab-stops: list =
.5in"><FONT=20
face=3DArial size=3D2>Validation-while-you-type with blue squiggles =
and error=20
list.<o:p></o:p> </FONT>
<LI class=3DMsoNormal=20
style=3D"MARGIN: 0in 0in 0pt; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto; mso-list: l0 level1 lfo1; tab-stops: list =
.5in"><FONT=20
face=3DArial size=3D2>Auto-completion of <?xml:namespace prefix =3D =
st1 ns =3D=20
"urn:schemas-microsoft-com:office:smarttags"=20
=
/><st1:PersonName><st1:PersonName>name</st1:PersonName></st1:PersonName>s=
pace=20
declarations, end tags and attribute value quotes.<o:p></o:p> </FONT>
<LI class=3DMsoNormal=20
style=3D"MARGIN: 0in 0in 0pt; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto; mso-list: l0 level1 lfo1; tab-stops: list =
.5in"><FONT=20
face=3DArial size=3D2>Support for xsi:schemaLocation and=20
xsi:noNamespaceSchemaLocation attributes.<o:p></o:p> </FONT>
<LI class=3DMsoNormal=20
style=3D"MARGIN: 0in 0in 0pt; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto; mso-list: l0 level1 lfo1; tab-stops: list =
.5in"><FONT=20
face=3DArial size=3D2>Schema picker dialog for overriding schemas =
used for=20
validation, which is then remembered as a document property in your=20
solution.<o:p></o:p> </FONT>
<LI class=3DMsoNormal=20
style=3D"MARGIN: 0in 0in 0pt; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto; mso-list: l0 level1 lfo1; tab-stops: list =
.5in"><FONT=20
face=3DArial size=3D2>Schema cache for commonly used schemas with =
standard set=20
provided out of the box. You can easily add your own schemas =
here or=20
edit the existing ones to constantly improve your XML editing=20
experience.<o:p></o:p> </FONT>
<LI class=3DMsoNormal=20
style=3D"MARGIN: 0in 0in 0pt; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto; mso-list: l0 level1 lfo1; tab-stops: list =
.5in"><FONT=20
face=3DArial size=3D2>Smart Formatter that is more than a pretty =
printer. It=20
honors and formatting of attributes that you may have done by hand and =
it=20
fixes up the most common mistakes people make in XML, like unquoted =
attribute=20
values.<o:p></o:p> </FONT>
<LI class=3DMsoNormal=20
style=3D"MARGIN: 0in 0in 0pt; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto; mso-list: l0 level1 lfo1; tab-stops: list =
.5in"><FONT=20
face=3DArial size=3D2>Smart indenting based on XML element =
depth.<o:p></o:p>=20
</FONT>
<LI class=3DMsoNormal=20
style=3D"MARGIN: 0in 0in 0pt; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto; mso-list: l0 level1 lfo1; tab-stops: list =
.5in"><FONT=20
face=3DArial size=3D2>Inline expand/collapse support.<o:p></o:p> =
</FONT>
<LI class=3DMsoNormal=20
style=3D"MARGIN: 0in 0in 0pt; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto; mso-list: l0 level1 lfo1; tab-stops: list =
.5in"><FONT=20
face=3DArial size=3D2>Easy navigation between start and end tags using =
brace=20
matching command (Ctrl+]) .<o:p></o:p> </FONT>
<LI class=3DMsoNormal=20
style=3D"MARGIN: 0in 0in 0pt; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto; mso-list: l0 level1 lfo1; tab-stops: list =
.5in"><FONT=20
face=3DArial size=3D2>Brace highlighting so you see which tags are =
being closed as=20
you type.<o:p></o:p> </FONT>
<LI class=3DMsoNormal=20
style=3D"MARGIN: 0in 0in 0pt; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto; mso-list: l0 level1 lfo1; tab-stops: list =
.5in"><FONT=20
face=3DArial size=3D2>Goto Definition command for navigating between =
elements and=20
their associated DTD, XDR or XSD schema definitions. This command can =
also=20
navigate from an entity reference to the entity definition in the=20
DTD.<o:p></o:p> </FONT>
<LI class=3DMsoNormal=20
style=3D"MARGIN: 0in 0in 0pt; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto; mso-list: l0 level1 lfo1; tab-stops: list =
.5in"><FONT=20
face=3DArial size=3D2>Tool tips that popup showing xsd:annotations for =
the element=20
or attribute under the mouse.<o:p></o:p> </FONT>
<LI class=3DMsoNormal=20
style=3D"MARGIN: 0in 0in 0pt; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto; mso-list: l0 level1 lfo1; tab-stops: list =
.5in"><FONT=20
face=3DArial size=3D2>XSL and XSD compilation errors while you type, =
providing=20
even more error checking that can be represented in the schemas=20
alone.<o:p></o:p> </FONT>
<LI class=3DMsoNormal=20
style=3D"MARGIN: 0in 0in 0pt; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto; mso-list: l0 level1 lfo1; tab-stops: list =
.5in"><FONT=20
face=3DArial><FONT size=3D2>Show XSLT Output command available on any =
XML or XSLT=20
file.<o:p></o:p></FONT></FONT></LI></UL>
<H3 style=3D"MARGIN: auto 0in"><SPAN style=3D"FONT-SIZE: 12pt"><FONT=20
face=3DArial><FONT size=3D2>XSD Schema=20
Inference<o:p></o:p></FONT></FONT></SPAN></H3>
<P><FONT face=3DArial><FONT size=3D2>The editor provides a handy command =
<st1:PersonName><st1:PersonName>name</st1:PersonName></st1:PersonName>d =
"Create=20
Schema" which does one of three things:<o:p></o:p></FONT></FONT></P>
<OL type=3D1>
<LI class=3DMsoNormal=20
style=3D"MARGIN: 0in 0in 0pt; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto; mso-list: l2 level1 lfo2; tab-stops: list =
.5in"><FONT=20
face=3DArial size=3D2>Convert associated DTD to XSD<o:p></o:p> </FONT>
<LI class=3DMsoNormal=20
style=3D"MARGIN: 0in 0in 0pt; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto; mso-list: l2 level1 lfo2; tab-stops: list =
.5in"><FONT=20
face=3DArial size=3D2>Convert associated XDR schema to XSD<o:p></o:p> =
</FONT>
<LI class=3DMsoNormal=20
style=3D"MARGIN: 0in 0in 0pt; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto; mso-list: l2 level1 lfo2; tab-stops: list =
.5in"><FONT=20
face=3DArial><FONT size=3D2>Infer a schema from the=20
XML<o:p></o:p></FONT></FONT></LI></OL>
<P><FONT face=3DArial><FONT size=3D2>This is by far the easiest way to =
get started=20
with designing an XSD schema.<o:p></o:p></FONT></FONT></P>
<H3 style=3D"MARGIN: auto 0in"><SPAN style=3D"FONT-SIZE: 12pt"><FONT=20
face=3DArial><FONT size=3D2>XSLT =
Debugging<o:p></o:p></FONT></FONT></SPAN></H3>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT =
face=3DArial><FONT size=3D2>In=20
non-Express SKU's only, this feature gives you a powerful XSLT debugger, =
fully=20
integrated into the overall Visual Studio debugging experience so you =
can step=20
from C# code directly into the XSLT transform itself and back out, or =
from XSLT=20
out to extension objects and back.<SPAN style=3D"mso-spacerun: =
yes"> =20
</SPAN>It also provides a =93Debug XSL=94 command on XML editor toolbar =
to start=20
debugging directly from XML or XSL file.<o:p></o:p></FONT></FONT></P>
<P><FONT face=3DArial><FONT size=3D2>Once debugging has started the =
standard Visual=20
Studio debugging menu is available including special support for the=20
following:<o:p></o:p></FONT></FONT></P>
<P=20
style=3D"MARGIN-LEFT: 0.5in; TEXT-INDENT: -0.25in; mso-list: l0 level1 =
lfo1; tab-stops: list .5in"><FONT=20
face=3DArial><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Symbol; mso-fareast-font-family: =
Symbol; mso-bidi-font-size: 12.0pt; mso-bidi-font-family: Symbol"><SPAN=20
style=3D"mso-list: Ignore">=B7<SPAN style=3D"FONT: 7pt 'Times New =
Roman'"><FONT=20
size=3D2> =20
</FONT></SPAN></SPAN></SPAN><FONT size=3D2>Setting and clearing =
breakpoints, at=20
the node level (as opposed to line level).<o:p></o:p></FONT></FONT></P>
<P=20
style=3D"MARGIN-LEFT: 0.5in; TEXT-INDENT: -0.25in; mso-list: l0 level1 =
lfo1; tab-stops: list .5in"><FONT=20
face=3DArial><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Symbol; mso-fareast-font-family: =
Symbol; mso-bidi-font-size: 12.0pt; mso-bidi-font-family: Symbol"><SPAN=20
style=3D"mso-list: Ignore">=B7<SPAN style=3D"FONT: 7pt 'Times New =
Roman'"><FONT=20
size=3D2> =20
</FONT></SPAN></SPAN></SPAN><FONT size=3D2>Locals window that shows XSLT =
variables=20
and parameters that are in scope.<o:p></o:p></FONT></FONT></P>
<P=20
style=3D"MARGIN-LEFT: 0.5in; TEXT-INDENT: -0.25in; mso-list: l0 level1 =
lfo1; tab-stops: list .5in"><FONT=20
face=3DArial><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Symbol; mso-fareast-font-family: =
Symbol; mso-bidi-font-size: 12.0pt; mso-bidi-font-family: Symbol"><SPAN=20
style=3D"mso-list: Ignore">=B7<SPAN style=3D"FONT: 7pt 'Times New =
Roman'"><FONT=20
size=3D2> =20
</FONT></SPAN></SPAN></SPAN><FONT size=3D2>Call Stack window that shows =
XSLT=20
template stack.<o:p></o:p></FONT></FONT></P>
<H3 style=3D"MARGIN: auto 0in"><SPAN style=3D"FONT-SIZE: 12pt"><FONT=20
face=3DArial><FONT size=3D2>Deep VS Integration &=20
Extensibility<o:p></o:p></FONT></FONT></SPAN></H3>
<DIV class=3DMsoNormal=20
style=3D"MARGIN: 0in 0in 0pt; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto; mso-list: l1 level1 lfo3; tab-stops: list =
.5in"><FONT=20
face=3DArial><FONT size=3D2>All the advanced core text editor commands =
and=20
configurability is available, for =
example:<o:p></o:p></FONT></FONT></DIV>
<UL type=3Ddisc>
<UL type=3Dcircle>
<LI class=3DMsoNormal=20
style=3D"MARGIN: 0in 0in 0pt; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto; mso-list: l1 level2 lfo3; tab-stops: list =
1.0in"><FONT=20
face=3DArial size=3D2>Fully configurable colors using standard=20
Tools/Options/Environment/Fonts and Colors property page.<o:p></o:p> =
</FONT>
<LI class=3DMsoNormal=20
style=3D"MARGIN: 0in 0in 0pt; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto; mso-list: l1 level2 lfo3; tab-stops: list =
1.0in"><FONT=20
face=3DArial size=3D2>Fully integrated text editor settings =
(Tools/Options/Text=20
Editor/XML) for general, tabs and miscellaneous settings.<o:p></o:p> =
</FONT>
<LI class=3DMsoNormal=20
style=3D"MARGIN: 0in 0in 0pt; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto; mso-list: l1 level2 lfo3; tab-stops: list =
1.0in"><FONT=20
face=3DArial size=3D2>Support for the new Visual Studio 2005 =
"Import/Export=20
Settings" feature.</FONT></LI></UL></UL>
<DIV class=3DMsoNormal=20
style=3D"MARGIN: 0in 0in 0pt; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto; mso-list: l1 level2 lfo3; tab-stops: list =
1.0in"><FONT=20
face=3DArial><FONT size=3D2>Support for multiple-views over the same =
buffer.<SPAN=20
style=3D"mso-spacerun: yes"> </SPAN>In Visual Studio 2003, the XSD =
designer=20
and grid views were only available from a tab at the bottom of the =
document=20
window, which means you could not view both ways at the same time. This=20
limitation has been removed, and each different view is now a full =
fledged=20
document window.<SPAN style=3D"mso-spacerun: yes"> =20
</SPAN><o:p></o:p></FONT></FONT></DIV>
<DIV class=3DMsoNormal=20
style=3D"MARGIN: 0in 0in 0pt; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto; mso-list: l1 level1 lfo3; tab-stops: list =
.5in"><FONT=20
face=3DArial size=3D2></FONT> </DIV>
<DIV class=3DMsoNormal=20
style=3D"MARGIN: 0in 0in 0pt; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto; mso-list: l1 level1 lfo3; tab-stops: list =
.5in"><FONT=20
face=3DArial><FONT size=3D2>Custom XML designers can also be registered =
per file=20
extension and/or XML=20
<st1:PersonName><st1:PersonName>name</st1:PersonName></st1:PersonName>spa=
ce URI,=20
which is how the Visual Studio XSD designer, DataSet designer, and the =
Grid View=20
are associated with the XML editor.<SPAN style=3D"mso-spacerun: =
yes"> =20
</SPAN>Anyone can now register an XML designer for a given=20
<st1:PersonName><st1:PersonName>name</st1:PersonName></st1:PersonName>spa=
ce and=20
the XML editor will automatically provide a View Designer menu item for =
invoking=20
that designer. In fact if you are planning a custom XML =
designer, I'd=20
love to chat about integration with this new XML text=20
editor.<o:p></o:p></FONT></FONT></DIV>
<P><FONT face=3DArial size=3D2>All feedback is welcome!</FONT></P>
<P><FONT face=3DArial size=3D2>XML Editor team,<BR>Microsoft.</FONT></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><o:p><FONT =
face=3DArial=20
size=3D2> </FONT></o:p></P>
<DIV><FONT face=3DArial size=3D2></FONT><FONT face=3DArial=20
size=3D2></FONT> </DIV></BODY></HTML>
------=_NextPart_000_00F7_01C45F01.90FA5F30--
|
|
| |
These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.
| |
| |
|
|
|
