.NET (Core and Framework)

Mike Dimmick30-Oct-07 6:51

Mike Dimmick

30-Oct-07 6:51

Debugging Your Visual Basic Application[^]

DoEvents: Generating unexpected recursion since 1991

tim63731-Oct-07 5:04

tim637

31-Oct-07 5:04

Thanks that was a good input.

tim637

Pete O'Hanlon30-Oct-07 23:19

Pete O'Hanlon

30-Oct-07 23:19

Add a Console.ReadKey() before the End Sub. This tells the program to wait for input from the keyboard.

Deja View - the feeling that you've seen this post before.

Database user ID/password

tim63731-Oct-07 5:03

tim637

31-Oct-07 5:03

Thanks that was a good in put.

tim637

#realJSOP30-Oct-07 3:51

Re: Database user ID/password

30-Oct-07 3:51

I created a new web site project, and added a database to it. How do I setup a user id and password to access the specific database? I tried to "modify connection" but it said something about the username is not associated with a trusted SQL server connection.

"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001

Ed.Poore30-Oct-07 4:20

30-Oct-07 4:20

Do you mean a username and password to access the SQL database through that rather than Windows Integrated Security (or whatever it's called), i.e. you specify the username and password to connect to the database?

If you're trying to connect through integrated security from ASP.NET chances are that that role has not been added to the permissions on the database. I.e. you need to create a user (server wide) for ASP.NET and then allow this user permission to read/write to the database in question.

A similar thing is required if you're using SQL Authentication rather than Integrated.

Of couse I may have misunderstood you completely.

Re: Database user ID/password

Pete O'Hanlon30-Oct-07 4:49

Pete O'Hanlon

30-Oct-07 4:49

The user Id/password that you use in the connection string relate to a user that is set up in the database. You would need to add a particular user to the database and set it up with the relevant permissions.

Deja View - the feeling that you've seen this post before.

SelectSingleNode Not Getting Node

#realJSOP29-Oct-07 12:04

29-Oct-07 12:04

What would cause SelectSingleNode to not retrieve the specified node?

I tried this:

XmlNode groupNode = root.SelectSingleNode("connectionStrings")

(root is "configuration").

I also tried this:

XmlNamespaceManager nm = new XmlNamespaceManager(doc.NameTable);
nm.AddNamespace("br", "C:\\web.config");
XmlNode groupNode = root.SelectSingleNode("//br:"+m_groupName, nm);

I always get a null response from SelectSingleNode, even though the section I'm looking for is really in the file.

Anyone?

Ed.Poore29-Oct-07 13:33

29-Oct-07 13:33

Can you post the relevant snippet of your xml file?

#realJSOP29-Oct-07 23:22

29-Oct-07 23:22

It's a "typical" web.config file generated completely within the VS2005 IDE.

Ed.Poore29-Oct-07 13:42

29-Oct-07 13:42

Ok, I think I might have got something working for you:
Xml File:

<?xml version="1.0"?>
<configuration xmlns:br="http://microsoft.com/schemas/VisualStudio/TeamTest/2006">
	<br:connectionStrings>
		<add name="SQL" connectionString="SQL" />
	</br:connectionStrings>
	<connectionStrings>
		<add name="SQL2" connectionString="SQL2" />
	</connectionStrings>
</configuration>

Code:

using System;
using System.Xml;

namespace ConsoleApplication1
{
	class Program
	{
		static void Main(string[] args)
		{
			XmlDocument dom = new XmlDocument();
			XmlNamespaceManager manager = new XmlNamespaceManager(dom.NameTable);
			manager.AddNamespace("br", "http://microsoft.com/schemas/VisualStudio/TeamTest/2006");

			dom.Load("Web.config");

			XmlNode groupNode = dom.DocumentElement.SelectSingleNode("br:connectionStrings", manager);

			if (groupNode == null)
				Console.WriteLine("(null)");
			else
				Console.WriteLine(groupNode["add"].Attributes["name"].Value);
		}
	}
}

Basically you need to construct the XmlNamespaceManager like you did but pass it into the SelectSingleNode function so that the function can use that object to resolve the namespaces in the XPath query.

Hope that helps, MS probably have their reasons for implementing it this way but it does seem a bit backwards, surely the NameTable should be populated from the xml file if that's where you read it from.

#realJSOP29-Oct-07 23:20

29-Oct-07 23:20

Thanks, I'll look at that when I get to work.

I initially tested my app with a simple web.config file. This file has your typical configuration section with a appSettings, connectionStrings, and a web.config section. That was working pretty well, so I decided to try it with one of our production web.config files (significantly larger and more complex). This file has the same stuff as the other one, as well as a configOptions section. A significant difference between the two files is that the production one has comments.

I'm trying to use Alvaro Mendez's read/write XML article [^] as a stepping off point because I haven't found ANY class that can handle the entire web.config file (none of them can read the connectionStrings section). His article doesn't do the namespace thing (and doesn't read the connectionStrings section), and seems to work fine on my small file, but chokes/pukes on the "real" config file.

Ed.Poore30-Oct-07 0:22

30-Oct-07 0:22

What I'm wondering is if this is a "standard" web.config why do you need namespaces?

#realJSOP30-Oct-07 2:42

30-Oct-07 2:42

I tried namespaces because of the stuff I found on the web regarding SelectSingleNode returning null. That didn't work any better than not using them. :/

Ed.Poore30-Oct-07 3:06

30-Oct-07 3:06

Hmm, I did have a problem with SelectSingleNode before now that you mention it, the work-around I had was to use the indexer of the collection and check whether it was null.

Perhaps there's a bug in the 2005 version, the code I supplied worked on VS2008 with 3.5 framework, I can retarget it to compile against the 2.0 framework if it's any help.

#realJSOP30-Oct-07 3:19

Re: SelectSingleNode Not Getting Node [modified]

30-Oct-07 3:19

I think I found my answer (detailed in another reply).

#realJSOP30-Oct-07 3:05

30-Oct-07 3:05

I figured out why it's not working. The web.config file in question has the following:

<configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0">

It therefore has a problem finding any section contained within the configuration section. When I delete the xmlns attribute, my code works. Any idea how to ignore this programatically? .Net doesn't seem to have a problem parsing this web.config...

-- modified at 9:13 Tuesday 30th October, 2007

I have found references on google that claim the xmlns attribute isn't needed. I'm going to go ahead and delete the attribute and see if the associated web site still works.

Ed.Poore30-Oct-07 4:17

30-Oct-07 4:17

Ok the problem seems to be that .NET 2.0 supports XPath 1.0 and XPath 1.0 does not support default namespaces. To get around this you can do the following (for some reason Confused | :confused:

):

Sample Xml File

<?xml version="1.0"?>
<configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0">
  <connectionStrings>
		<add name="SQL" connectionString="SQL" />
	</connectionStrings>
</configuration>

Sample code:

using System;
using System.Xml;

namespace ConsoleApplication1
{
	class Program
	{
		static void Main(string[] args)
		{
			XmlDocument dom = new XmlDocument();
			dom.Load("Web.config");

			XmlNamespaceManager manager = new XmlNamespaceManager(dom.NameTable);
			manager.AddNamespace("default", "http://schemas.microsoft.com/.NetConfiguration/v2.0");

			XmlNode node = dom.DocumentElement.SelectSingleNode("default:connectionStrings", manager);

			if (node == null)
				Console.WriteLine("(null)");
			else
				Console.WriteLine(node.OuterXml);
		}
	}
}

Notice where I added the default namespace with a assigned name default, the documentation says that the default namespace should be string.Empty but this does not work, if you give it a namespace then it does.

Hopefully it'll support XPath 2.0 at some point.