What do you want to know about VS 2010?
-
Not to start overly negative - but a statement about maintenance policy would be nice. Any statement - including "we won't fix it unless it sets the office on fire - repeatedly" - would be betther than the frustrating experience MS connect is now. I.e. what kind of bugs/feature requests are considered for initial release, for SP1 etc. (But maybe that's beyond your area of influence) Other than that - Any improvements to Help? Any changes to the Add-In API / documentaiton / deplyoment?
Personally, I love the idea that Raymond spends his nights posting bad regexs to mailing lists under the pseudonym of Jane Smith. He'd be like a super hero, only more nerdy and less useful. [Trevel]
| FoldWithUs! | sighist | µLaunch - program launcher for server core and hyper-v server -
The Code Project is launching a Virtual Conference in March on VS 2010 and we're working on what content we should include for our sessions. What do you guys want to understand better/ learn how to do when it comes to VS 2010?? We're thinking tips and tricks, top five or ten lists, and do's and don'ts...? Thanks for your help! Andrea Penner
I'd like to know that it's fit for purpose. All the indications so far are that it isn't, and as a result we'll be skipping this release. http://msmvps.com/blogs/carlosq/archive/2009/12/07/no-public-vs-2010-beta-3-or-release-candidate.aspx[^]
Anna :rose: Tech Blog | Visual Lint "Why would anyone prefer to wield a weapon that takes both hands at once, when they could use a lighter (and obviously superior) weapon that allows you to wield multiple ones at a time, and thus supports multi-paradigm carnage?"
-
Eitherway, this is all helpful information. Anything else? Any other particular pain points we could address?
The automation model. Specifically, the new Code Model and all of the broken bits in the Command Bar interfaces. Detail on the changes to the Visual Studio SDK (and especially any impacts on backware compatibility) would also be useful. e.g. How do the editor changes impact packages providing colouriser and refactoring support?
Anna :rose: Tech Blog | Visual Lint "Why would anyone prefer to wield a weapon that takes both hands at once, when they could use a lighter (and obviously superior) weapon that allows you to wield multiple ones at a time, and thus supports multi-paradigm carnage?"
-
The Code Project is launching a Virtual Conference in March on VS 2010 and we're working on what content we should include for our sessions. What do you guys want to understand better/ learn how to do when it comes to VS 2010?? We're thinking tips and tricks, top five or ten lists, and do's and don'ts...? Thanks for your help! Andrea Penner
I have been trying to get a C# app to read an XML file data and element attributes. via it's named elements using DOT-Notation like actionscript. I have been beating myself senseless trying to figure out how. Right now all i can get from an XML file is the element values but not their attributes. Any help on this would be great.
-
The Code Project is launching a Virtual Conference in March on VS 2010 and we're working on what content we should include for our sessions. What do you guys want to understand better/ learn how to do when it comes to VS 2010?? We're thinking tips and tricks, top five or ten lists, and do's and don'ts...? Thanks for your help! Andrea Penner
I'm interested in the support for SharePoint, both 2010 and 2007. I understand SharePoint 2010 will be able to be installed on a Windows 7 platform so I don't have to run my development tools on a server.
I know the language. I've read a book. - _Madmatt
-
I have been trying to get a C# app to read an XML file data and element attributes. via it's named elements using DOT-Notation like actionscript. I have been beating myself senseless trying to figure out how. Right now all i can get from an XML file is the element values but not their attributes. Any help on this would be great.
I'm a little confused with what your looking for here. I think you maybe looking to do this in the "new style, .net 4.0" way of using dynamic data, is that right? I will be glad to help you do it the old style way that involves creating a .xsd schema for your xml file. I have used this way many times and it works great.
-
I'm a little confused with what your looking for here. I think you maybe looking to do this in the "new style, .net 4.0" way of using dynamic data, is that right? I will be glad to help you do it the old style way that involves creating a .xsd schema for your xml file. I have used this way many times and it works great.
example: >people< >person sex="male"< >name<Some Name>/name< >/person< >/people< ActionScript: var Sex:String = xmlReader.person.@sex; var Name:String = xmlReader.person.name; I have this for reading XML element values (applied within another project I made): private void btnImport_Click(object sender, EventArgs e) { OpenFileDialog oDlg = new OpenFileDialog(); oDlg.InitialDirectory = "C:\\"; oDlg.Filter = "xml Files|*.xml"; if (oDlg.ShowDialog() == DialogResult.OK) { XmlDocument xmlBranding = new XmlDocument(); xmlBranding.Load(oDlg.FileName); if (File.Exists(oDlg.FileName)) { xmlBranding.Load(oDlg.FileName); XmlElement elmBranding = xmlBranding.DocumentElement; XmlNodeList lstBranding = elmBranding.ChildNodes; for (int index = 0; index < lstBranding.Count; index++) { switch (lstBranding[index].LocalName) { case "LogoImageRef": txtLogoImageRef.Text = lstBranding[index].InnerText; break; case "SystemManufacturer": txtSystemManufacturer.Text = lstBranding[index].InnerText; break; case "SystemModel": txtSystemModel.Text = lstBranding[index].InnerText; break; case "SupportPhone": if (lstBranding[index].InnerText != "") { chkSupportPhone.Checked = true; txtSupportPhone.Text = lstBranding[index].InnerText; } break; case "SupportURL": if (lstBranding[index].InnerText != "") { chkSupportWeb.Checked = true; txtSupportURL.Text = lstBranding[index].InnerText; } break; case "SupportHours":
-
example: >people< >person sex="male"< >name<Some Name>/name< >/person< >/people< ActionScript: var Sex:String = xmlReader.person.@sex; var Name:String = xmlReader.person.name; I have this for reading XML element values (applied within another project I made): private void btnImport_Click(object sender, EventArgs e) { OpenFileDialog oDlg = new OpenFileDialog(); oDlg.InitialDirectory = "C:\\"; oDlg.Filter = "xml Files|*.xml"; if (oDlg.ShowDialog() == DialogResult.OK) { XmlDocument xmlBranding = new XmlDocument(); xmlBranding.Load(oDlg.FileName); if (File.Exists(oDlg.FileName)) { xmlBranding.Load(oDlg.FileName); XmlElement elmBranding = xmlBranding.DocumentElement; XmlNodeList lstBranding = elmBranding.ChildNodes; for (int index = 0; index < lstBranding.Count; index++) { switch (lstBranding[index].LocalName) { case "LogoImageRef": txtLogoImageRef.Text = lstBranding[index].InnerText; break; case "SystemManufacturer": txtSystemManufacturer.Text = lstBranding[index].InnerText; break; case "SystemModel": txtSystemModel.Text = lstBranding[index].InnerText; break; case "SupportPhone": if (lstBranding[index].InnerText != "") { chkSupportPhone.Checked = true; txtSupportPhone.Text = lstBranding[index].InnerText; } break; case "SupportURL": if (lstBranding[index].InnerText != "") { chkSupportWeb.Checked = true; txtSupportURL.Text = lstBranding[index].InnerText; } break; case "SupportHours":
You'll need to use the "xsd" utility code generator. Although I used vs 2010 you could use any all the way back to VS 2003. Ok so from this create a file named people.xml:
<?xml version="1.0" encoding="utf-8"?>
<people>
<person sex="male">
<name>Donnald Duck</name>
</person>
<person sex="female">
<name>Minnie Mouse</name>
</person>
<person sex="female">
<name>Daisy Duck</name>
</person>
<person sex="female">
<name>Willma Flintstone</name>
</person>
<person sex="male">
<name>Barney Rubble</name>
</person>
<person sex="male">
<name>Fred Flintstone</name>
</person>
<person sex="female">
<name>Jessica Rabbit</name>
</person>
<person sex="male">
<name>Bambam Rubble</name>
</person>
<person sex="female">
<name>Pebbles Flintstone</name>
</person>
</people>From here use xsd as follows: >xsd people.xml To generate an initial .xsd file from your .xml file. This should give you something like this:
<?xml version="1.0" encoding="utf-8"?>
<xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema" >
<xs:element name="people">
xs:complexType
<xs:choice minOccurs="0" maxOccurs="unbounded">
<xs:element name="person" minOccurs="1" maxOccurs="unbounded">
xs:complexType
xs:sequence
<xs:element name="name" type="xs:string" minOccurs="1" maxOccurs="1" />
</xs:sequence>
<xs:attribute name="sex" type="xs:string" />
</xs:complexType>
</xs:element>
</xs:choice>
</xs:complexType>
</xs:element>
</xs:schema>Once you have this you can generate some .cs code you'll need to define the structure in c# terms. > xsd /c /n:PeopleDemo people.xsd This will generate a file named people.cs. Then you just need some code to load it and work it. I have created a Console app and put this in the Program.cs file of the project the people.cs file has to be add to the project as well. The two classes are part of my bag of tricks I wrote some time ago. Here's the code:
-
You'll need to use the "xsd" utility code generator. Although I used vs 2010 you could use any all the way back to VS 2003. Ok so from this create a file named people.xml:
<?xml version="1.0" encoding="utf-8"?>
<people>
<person sex="male">
<name>Donnald Duck</name>
</person>
<person sex="female">
<name>Minnie Mouse</name>
</person>
<person sex="female">
<name>Daisy Duck</name>
</person>
<person sex="female">
<name>Willma Flintstone</name>
</person>
<person sex="male">
<name>Barney Rubble</name>
</person>
<person sex="male">
<name>Fred Flintstone</name>
</person>
<person sex="female">
<name>Jessica Rabbit</name>
</person>
<person sex="male">
<name>Bambam Rubble</name>
</person>
<person sex="female">
<name>Pebbles Flintstone</name>
</person>
</people>From here use xsd as follows: >xsd people.xml To generate an initial .xsd file from your .xml file. This should give you something like this:
<?xml version="1.0" encoding="utf-8"?>
<xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema" >
<xs:element name="people">
xs:complexType
<xs:choice minOccurs="0" maxOccurs="unbounded">
<xs:element name="person" minOccurs="1" maxOccurs="unbounded">
xs:complexType
xs:sequence
<xs:element name="name" type="xs:string" minOccurs="1" maxOccurs="1" />
</xs:sequence>
<xs:attribute name="sex" type="xs:string" />
</xs:complexType>
</xs:element>
</xs:choice>
</xs:complexType>
</xs:element>
</xs:schema>Once you have this you can generate some .cs code you'll need to define the structure in c# terms. > xsd /c /n:PeopleDemo people.xsd This will generate a file named people.cs. Then you just need some code to load it and work it. I have created a Console app and put this in the Program.cs file of the project the people.cs file has to be add to the project as well. The two classes are part of my bag of tricks I wrote some time ago. Here's the code:
I'll have to get back to you on this. I'm just a little lost. I started breaking into the new concepts of C# 2 years ago from studying C/C++ a long time ago. I'll have to look alot of this up.
-
"If we don't use it, noone else will". (I have a bookmark of a blog post somewhere...) - i.e. the idea was to use it in a large, project so they can work out the kinks. If you ask me, the VS guys lost a bet.
Personally, I love the idea that Raymond spends his nights posting bad regexs to mailing lists under the pseudonym of Jane Smith. He'd be like a super hero, only more nerdy and less useful. [Trevel]
| FoldWithUs! | sighist | µLaunch - program launcher for server core and hyper-v server