The given key was not present in the dictionary? FileUltimate
Question asked by Barclay Berger - October 14, 2014 at 1:46 PM
Answered
when I open examples or create new project and reference dll and add control I get the error in both?  What am I missing?

7 Replies

Reply to Thread
0
Cem Alacayir Replied
Employee Post Marked As Answer
This error is not FileUltimate related, it's Visual Studio related:
 
One of Visual Studio’s most cryptic error messages is Server Explorer’s infamous “the given key was not present in the dictionary.” This typically means that you’ve installed a custom data provider, created a Server Explorer connection using that provider, and then uninstalled the provider without deleting the Server Explorer entry.  This pretty much kills Server Explorer: from now on, any time you try to add or remove a connection, it barfs up the useless error.  This means you can’t even remove the dud connection.
 
I guess this link will solve your problem:
0
yeah that link fix didn't work. Your control seems to be the only thing affected by this in Visual Studio. I've tried on 2012 and 2013 same error. I've tried on two different pc's same results. I guess my VS is broken
0
Cem Alacayir Replied
Employee Post
When exactly do you get the error? For example, do you get it immediately after you open Example project with Visual Studio? Or do you get the error when you run the project? Strange that it happened on 2 different machines. If it turns out a FileUltimate bug we will fix it immediately. However it's first time we hear this error. By the way, the fix in that link specifies paths according to Visual Studio 2010 so you may try the correct paths for 2012 or 2013 (like 11.0 , 12.0 etc)
0
Yeah I got the paths correct, when I open any of the examples and view in design the control has the error in it. If I create a new project and add the dll then add the control to the page, view in design, get the error.
0
Cem Alacayir Replied
Employee Post
Ah ok, now I understand the problem. Unfortunately Design view is not supported, so this behavior is expected. You can just ignore the error. Edit the page in Markup view to change properties of control.
0
Oh, it used to be in my version 3.2 so I expected the same in new. Ok Thanks
0
Rob Wells Replied
Hi there... I'm experiencing the same problem after trying to install a trial version of FileUltimate. It happens when I load the ASPX page in my browser. If it's relevant, I'm not using design view at all. The linked fix did not work. I tried to drop it onto a barebones ASPX page with nothing else in it. Any thoughts?

Reply to Thread