I found a weird behavior in VS2015 Here are the details:
I have a .Net 4.6 project referencing a 3.5 assembly. This assembly defines in one of it's interfaces the following method that I was able to inspect using Resharper decompiler.
void WriteString([MarshalAs(UnmanagedType.BStr), In] string data, [In] bool flushAndEND = true);
Take note of the last optional argument flushAndEND which has a default value of true. The problem now is when I use this method in my project, hovering over the method name shows the usual VS toolTip which details the method signature, except that for me it shows a wrong default value of the optional argument flushAndEND. Here's a screenshot
To make things even worse, I have noticed that during runtime, when calling the method WriteStringwith only the first parameter, flushAndEND gets set to false and not its default value defined in the DLL I'm referencing. The impact of this on our project was big because it rendered a big feature of our app useless and blocked a big part of our regression tests.
I was able to overcome this problem by forcing the value of the optional argument to true when calling the method, but I'm afraid there are other calls somewhere else in the project that suffer from the same problem. So I will need a better solution for this or to at least understand what's the cause behind this behavior.
We've just upgraded our environment weeks ago. Before we were using VS2013 and everything worked fine.
I am aware of the confirmed .Net 4.6 bug which causes some arguments to be passed wrong values and I can relate it to my issue here, but as it is said in the article, the bug only occurs when compiling for x64 architecture. My project is a WPF application and we compile it to be x32.
Why is WriteString called with wrong default argument?
I will try later to isolate the problem in a small project and see if I can reproduce the problem.
EDIT: I've managed to isolate the problem, and found some interesting stuff!
I created a simple .Net 4.6 console application, added a reference to my Dll and wrote the following simple code that consist of sending a command to a device and reading the response:
private static void Main(string[] args)
{
//Init managers
ResourceManager ioMgr = new ResourceManagerClass();
FormattedIO488 instrument = new FormattedIO488Class();
//Connect to the USB device
instrument.IO = (IMessage)ioMgr.Open("USB0::0x0957::0x0909::MY46312358::0::INSTR");
string cmd = "*IDN?";
//This is the problematic method from my dll
instrument.WriteString(cmd);
//Read the response
string responseString = instrument.ReadString();
Console.WriteLine(responseString);
Console.ReadKey();
}
What I did next, is open this project from both VS 2013 and VS 2015. In both versions of VS I did rebuild the project and run it. Here are the results:
VS2013: WriteString was called using the CORRECT default value of flushAndEND (which is true meaning flush the buffer and end the command).
VS2015: WriteString was called using the WRONG default value of flushAndEND which gave a timeout exception.
Further inspections between the two versions of Visual Studio shows that the object browser viewer in VS2013 shows the method signature as:
void WriteString(string data, [bool flushAndEND = True])
while the object browser in VS2015 shows the method signature as:
void WriteString(string data, [bool flushAndEND = False])
The only explanation of this behavior is that there's a problem with VS2015 compiler not reading correct default values from the assembly.