Visual Basic

For Each node1 In list1
            Dim val As String
            val = node1.Attributes("PN").Value
            If val = TextBox1.Text Then
                Dim list2 As XmlNodeList = node1.SelectNodes("Height")
                Dim node2 As XmlNode
                For Each node2 In list2
                    Dim val2 As String
                    val2 = node2.Attributes("DN").Value
                    If val2 = TextBox2.Text Then
                        TextBox3.Text = node2.InnerText
                    End If
                Next
            End If
        Next

<PN> 

<PN PN="1.6">

Gregory.Gadow wrote:

I'm pretty sure you can add other versioning databases than just VSS.

- Project/bin/ which contains your builds

*/bin */obj *.bak *.*scc *.user *.suo *.webinfo bin obj *.pdb *.exe *.DCS *.zip

Peter Trevor wrote:

However, in a professional setting you may sometimes encounter a discipline called “configuration management”. (This is, essentially, management of the whole software lifecycle and integrates “change management”, “repository management”, “release management”, etc, into a coherent whole.) In configuration management it is common to include the final deliverables (*.exe, *.dll, etc) under version control.

Peter Trevor wrote:

As general advice I’d say, unless you are short of disk space, if in doubt add it in. Better to have an unnecessary file in the repository than to discover after the fact that you’ve lost the specific version of a key file.

jschell wrote:

However one would then also expect that there would be a process step(s) which is specific to building as well. And it should start with a clean extract.Consequently one would not check in source/proj/etc files at the same time as deliverables.

jschell wrote:

Better to figure out what files are actually required. It becomes obvious with a clean extract.

CDMTJX wrote:

I think .resx is generated by Visual Studio...