Jump to content
Path To Custom Assembly Getting Altered When Switching Between V4.38.02 And V2.38.02
4 replies to this topic
Posted 06 February 2012 - 03:12 AM
e.g. In v2 I create a LinqToSQL custom assembly connection with this path:
'C:\Users\Jeremy Thomas\Documents\Visual Studio 2010\Projects\CodePlex\RapidDevBookCode\LLBL Pro v3.1\AW.LinqToSQL\bin\Debug\AW.LinqToSQL.dll'
And when I open in it v4 it shows '\Visual Studio 2010\Projects\CodePlex\RapidDevBookCode\LLBL Pro v3.1\AW.LinqToSQL\bin\Debug\AW.LinqToSQL.dll'
If I correct in v4 the next time I open up v2 it is has got the 'C:\Users\Jeremy Thomas\Documents' part missing and if I correct it goes back to square one again.
I have only see this happen on one machine but I happens with other Custom Typed Data Context Drivers such as entity framework as well.
Posted 11 February 2012 - 05:15 PM
Can you open up the ConnectionsV2.xml file in %appdata%\linqpad and let me know what LINQPad is saving to the encoded assembly path is for that connection?
Posted 12 February 2012 - 12:11 AM
When it is working in v4
<CustomAssemblyPathEncoded><MyDocuments>\Visual Studio 2010\Projects\CodePlex\RapidDevBookCode\LLBL Pro v3.1\AW.LinqToSQL\bin\Debug\AW.LinqToSQL.dll</CustomAssemblyPathEncoded>
When is is working in v2
<CustomAssemblyPathEncoded><Personal>\Visual Studio 2010\Projects\CodePlex\RapidDevBookCode\LLBL Pro v3.1\AW.LinqToSQL\bin\Debug\AW.LinqToSQL.dll</CustomAssemblyPathEncoded>
Posted 27 February 2012 - 12:05 AM
Thanks for the info. This will be fixed for the next build (very soon).
Interestingly, what caused the error is that the Environment.SpecialFolder enum defines MyDocuments and Personal with the same value (5).
Posted 07 March 2012 - 01:26 AM
Yep works now - thanks
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users