IXMLDOMDocument" has no member "selectSingleNode

Question

0.00/5 (No votes)

See more:

Hi,
I have migrated my project from VS2012 to VS2015 and currently I am getting error

#import <msxml.tli>

#import <msxml.tli

>

MSXML::IXMLDOMDocumentPtr gl_pDOMDoc[2] ={NULL,NULL};

C#

try
	{
		ConvertSpecialCharToString(strNewKey );//HSS_03152010
		m_strKeypath  = m_strETool + "//" + strkeyLocalMachine + "//" + strNewKey;
		ProcessKeyPath(m_strKeypath);//SSM_03182010
		
		IXMLDOMNodePtr  pResultnode=NULL;
		pResultnode =gl_pDOMDoc[m_bEnabledEncryption]->selectSingleNode((_bstr_t)m_strKeypath.AllocSysString()); //PDU_03312015  // m_pDOMDoc changed to gl_pDOMDoc[m_bEnabledEncryption]

		if(!pResultnode)
		{
			SearchPathTillCurrentPath(m_strKeypath);			
			bStatus =BS_SUCCESS;
		}
		else
			bStatus = BS_SUCCESS;

	}

C#

catch(...)
	{
		CString strLog;
		strLog.Format("Exception raised while creating key %s" ,m_strKeypath);
		LogError(LINE_INFO + strLog); 
		bStatus = BS_FAIL;
	}

The same code I am using is running successfully in VS2012 but it gives error with VS2015.

I am not able to understand the reason ..?

Posted 20-Dec-15 22:23pm

Thakur JAI SINGH

Updated 13-Mar-16 4:27am

v4

Add a Solution

Comments

CHill60 21-Dec-15 4:56am

Nor are we. Largely because we can't see your code.

Thakur JAI SINGH 21-Dec-15 5:25am

Thanks I have updated the code.

KarstenK 21-Dec-15 12:46pm

selectSingleNode((_bstr_t)m_strKeypath.AllocSysString());
the SysString must be freed. Memory leak!!!

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Rathore Amit · Answer 1 · 2016-03-13T04:27:00

Solution 1

try using #import <msxml6.dll> instead.

Posted 13-Mar-16 4:27am

Rathore Amit