Home
Help
Register
Log in

Search

 
   Active Threads  

You are here: Home > LLBLGen Pro > Bugs & Issues> Derived Models UpdateFromXXX method compile error when 'generate as nullable type' is false
 

Pages: 1 2
Bugs & Issues
Derived Models UpdateFromXXX method compile error when 'generate as nullable type' is false
Page:1/2 

  Print all messages in this thread  
Poster Message
TomDog
User



Location:
Wellington, New Zealand
Joined on:
25-Oct-2005 22:21:17
Posted:
570 posts
# Posted on: 01-Mar-2018 09:17:03. Goto attachments  
Example using Northwind, I have a model derived from Product, if I set one of the nullable entity fields, such as ReorderLevel, to have 'generate as nullable type' false the resulting UpdateFromProduct method has this compilation error - Cannot implicitly convert type 'short?' to 'short'.
Code:
public static void UpdateFromProduct(this Northwind.DAL.EntityClasses.ProductEntity toUpdate, Dm.DtoClasses.Product dto)
        {
            if((toUpdate == null) || (dto==null))
            {
                return;
            }
            toUpdate.CategoryId = dto.CategoryId;
            toUpdate.Discontinued = dto.Discontinued;
            toUpdate.ProductName = dto.ProductName;
            toUpdate.QuantityPerUnit = dto.QuantityPerUnit;
            toUpdate.ReorderLevel = dto.ReorderLevel;
            toUpdate.SupplierId = dto.SupplierId;
            toUpdate.UnitPrice = dto.UnitPrice;
            toUpdate.UnitsInStock = dto.UnitsInStock;
            toUpdate.UnitsOnOrder = dto.UnitsOnOrder;
        }
I can fix it manually by changing this line: toUpdate.ReorderLevel = dto.ReorderLevel.Value;

In summary the problem that the generation of the field in the derived model ignores the 'generate as nullable type' setting

LLBL v5.2.6
Jeremy Thomas
VS 2017 C#, LLBLGen v5.4, Winforms, WPF and ASP.NET MVCLLBL & LinqPad
 
Top
Otis
LLBLGen Pro Team



Location:
The Hague, The Netherlands
Joined on:
17-Aug-2003 18:00:36
Posted:
38090 posts
# Posted on: 01-Mar-2018 11:02:07.  
Hmm, this does sound familiar. Looking into it.

(edit) familiarity was about something else. I was thinking about how to fix this and it's indeed best to simply read the .Value property instead of making the DTO field also non-numerable.



Frans Bouma
LLBLGen Pro / ORM Profiler Lead Developer | Blog | Twitter
 
Top
Otis
LLBLGen Pro Team



Location:
The Hague, The Netherlands
Joined on:
17-Aug-2003 18:00:36
Posted:
38090 posts
# Posted on: 02-Mar-2018 11:45:39.  
The attached project is a bit cumbersome. It contains references to type converters which aren't needed for the issue and contains oracle meta-data which isn't needed, and it has the adapter specific folders not specified so it generates things in 1 folder, which gives a bit of a problem. All entities seem to have an attribute on them that's not defined in the project settings so manually removing that was a bit time consuming. Additionally, namespaces too... and typedviews have a custom base class which obviously doesn't exist in the generated code. Dissapointed I've spent over an hour cleaning this up.

Manually fixing this makes it usable to generate a repro, but I'd like to ask you to clean up the repro projects next time, thanks.

Looking into a fix for this....
Frans Bouma
LLBLGen Pro / ORM Profiler Lead Developer | Blog | Twitter
 
Top
Otis
LLBLGen Pro Team



Location:
The Hague, The Netherlands
Joined on:
17-Aug-2003 18:00:36
Posted:
38090 posts
# Posted on: 02-Mar-2018 14:29:57.  
It was a bit of a struggle, but it's fixed Regular Smiley See hotfix v5.2.7 and v5.3.4

Frans Bouma
LLBLGen Pro / ORM Profiler Lead Developer | Blog | Twitter
 
Top
TomDog
User



Location:
Wellington, New Zealand
Joined on:
25-Oct-2005 22:21:17
Posted:
570 posts
# Posted on: 07-Mar-2018 08:13:43.  
Thanks for sorting that, I'll make more effort with project file next time (I didn't really expect you to attempt to generate code form it), though I will say it would be make it easier if there was reference project for doing bug repro's.

I'm slightly curious as to why you went with using .Value rather than making the DTO field match the entity field.

Also I noticed the namespace of the built-in type converters changed from SD.LLBLGen.Pro.TypeConverters to SD.LLBLGen.Pro.ORMSupportClasses in the .llblgenproj file after I saved it in the new version, why was that?
Jeremy Thomas
VS 2017 C#, LLBLGen v5.4, Winforms, WPF and ASP.NET MVCLLBL & LinqPad
 
Top
Otis
LLBLGen Pro Team



Location:
The Hague, The Netherlands
Joined on:
17-Aug-2003 18:00:36
Posted:
38090 posts
# Posted on: 07-Mar-2018 10:17:19.  
TomDog wrote:
Thanks for sorting that, I'll make more effort with project file next time (I didn't really expect you to attempt to generate code form it), though I will say it would be make it easier if there was reference project for doing bug repro's.

That's a problem though: bugs often occur in edge cases, so you need a specific model which illustrates the problem, if it's common we'd run into it by now Wink E.g. a particular inheritance setup combined with a particular query.

Quote:

I'm slightly curious as to why you went with using .Value rather than making the DTO field match the entity field.

That would have been a breaking change. Both fields are nullable (the dto field derives its type from the field it's mapped on) and only the llblgen pro framework has a setting for not generating a nullable field as nullable, a leftover from v2. If the dto field now would 'inherit' this option, the field would become non-nullable as well, which would break code assuming it was nullable.

Quote:

Also I noticed the namespace of the built-in type converters changed from SD.LLBLGen.Pro.TypeConverters to SD.LLBLGen.Pro.ORMSupportClasses in the .llblgenproj file after I saved it in the new version, why was that?

So you load a project which has system type converters and when you save it it changes these in sd.llblgen.pro.ormsupport classes typeconverters in the llblgenproj file?

Can't reproduce it:            
Code:
<FieldMapping FieldName="Quantity" TargetFieldName="Quantity" TypeConverterToUse="SD.LLBLGen.Pro.TypeConverters.BooleanNumericConverter" />

stays the same.


Frans Bouma
LLBLGen Pro / ORM Profiler Lead Developer | Blog | Twitter
 
Top
TomDog
User



Location:
Wellington, New Zealand
Joined on:
25-Oct-2005 22:21:17
Posted:
570 posts
# Posted on: 09-May-2018 04:50:05.  
Otis wrote:
Quote:
Also I noticed the namespace of the built-in type converters changed from SD.LLBLGen.Pro.TypeConverters to SD.LLBLGen.Pro.ORMSupportClasses in the .llblgenproj file after I saved it in the new version, why was that?
So you load a project which has system type converters and when you save it it changes these in sd.llblgen.pro.ormsupport classes typeconverters in the llblgenproj file?

Can't reproduce it:            
Code:
<FieldMapping FieldName="Quantity" TargetFieldName="Quantity" TypeConverterToUse="SD.LLBLGen.Pro.TypeConverters.BooleanNumericConverter" />
stays the same.
Yes.

I've reproduced it by loading my project as a parameter to the designer and in the log I get this
Code:
PluginStore::Successfully loaded plug-in 'Project Inspector Plug-in' from assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.2\Plugins\SD.LLBLGen.Pro.Plugins.dll'.
Project File I/O::The typeconverter 'SD.LLBLGen.Pro.TypeConverters.Int32DecimalConverter' wasn't found, however a typeconverter with the same name in a different namespace was: 'SD.LLBLGen.Pro.ORMSupportClasses.Int32DecimalConverter', which is used instead.
Project File I/O::The typeconverter 'SD.LLBLGen.Pro.TypeConverters.Int32DecimalConverter' wasn't found, however a typeconverter with the same name in a different namespace was: 'SD.LLBLGen.Pro.ORMSupportClasses.Int32DecimalConverter', which is used instead.
Project File I/O::The typeconverter 'SD.LLBLGen.Pro.TypeConverters.SingleDecimalConverter' wasn't found, however a typeconverter with the same name in a different namespace was: 'SD.LLBLGen.Pro.ORMSupportClasses.SingleDecimalConverter', which is used instead.
Project File I/O::The typeconverter 'SD.LLBLGen.Pro.TypeConverters.SingleDecimalConverter' wasn't found, however a typeconverter with the same name in a different namespace was: 'SD.LLBLGen.Pro.ORMSupportClasses.SingleDecimalConverter', which is used instead.
Project File I/O::The typeconverter 'SD.LLBLGen.Pro.TypeConverters.SingleDecimalConverter' wasn't found, however a typeconverter with the same name in a different namespace was: 'SD.LLBLGen.Pro.ORMSupportClasses.SingleDecimalConverter', which is used instead.
Project File I/O::The typeconverter 'SD.LLBLGen.Pro.TypeConverters.SingleDecimalConverter' wasn't found, however a typeconverter with the same name in a different namespace was: 'SD.LLBLGen.Pro.ORMSupportClasses.SingleDecimalConverter', which is used instead.
Project File I/O::The typeconverter 'SD.LLBLGen.Pro.TypeConverters.SingleDecimalConverter' wasn't found, however a typeconverter with the same name in a different namespace was: 'SD.LLBLGen.Pro.ORMSupportClasses.SingleDecimalConverter', which is used instead.
Project File I/O::The typeconverter 'SD.LLBLGen.Pro.TypeConverters.SingleDecimalConverter' wasn't found, however a typeconverter with the same name in a different namespace was: 'SD.LLBLGen.Pro.ORMSupportClasses.SingleDecimalConverter', which is used instead.
Project File I/O::The typeconverter 'SD.LLBLGen.Pro.TypeConverters.SingleDecimalConverter' wasn't found, however a typeconverter with the same name in a different namespace was: 'SD.LLBLGen.Pro.ORMSupportClasses.SingleDecimalConverter', which is used instead.
Project File I/O::The typeconverter 'SD.LLBLGen.Pro.TypeConverters.SingleDecimalConverter' wasn't found, however a typeconverter with the same name in a different namespace was: 'SD.LLBLGen.Pro.ORMSupportClasses.SingleDecimalConverter', which is used instead.
Project File I/O::The typeconverter 'SD.LLBLGen.Pro.TypeConverters.SingleDecimalConverter' wasn't found, however a typeconverter with the same name in a different namespace was: 'SD.LLBLGen.Pro.ORMSupportClasses.SingleDecimalConverter', which is used instead.
Project File I/O::The typeconverter 'SD.LLBLGen.Pro.TypeConverters.SingleDecimalConverter' wasn't found, however a typeconverter with the same name in a different namespace was: 'SD.LLBLGen.Pro.ORMSupportClasses.SingleDecimalConverter', which is used instead.
Project File I/O::The typeconverter 'SD.LLBLGen.Pro.TypeConverters.SingleDecimalConverter' wasn't found, however a typeconverter with the same name in a different namespace was: 'SD.LLBLGen.Pro.ORMSupportClasses.SingleDecimalConverter', which is used instead.
Project File I/O::The typeconverter 'SD.LLBLGen.Pro.TypeConverters.SingleDecimalConverter' wasn't found, however a typeconverter with the same name in a different namespace was: 'SD.LLBLGen.Pro.ORMSupportClasses.SingleDecimalConverter', which is used instead.
Project File I/O::The typeconverter 'SD.LLBLGen.Pro.TypeConverters.SingleDecimalConverter' wasn't found, however a typeconverter with the same name in a different namespace was: 'SD.LLBLGen.Pro.ORMSupportClasses.SingleDecimalConverter', which is used instead.
Project File I/O::The typeconverter 'SD.LLBLGen.Pro.TypeConverters.SingleDecimalConverter' wasn't found, however a typeconverter with the same name in a different namespace was: 'SD.LLBLGen.Pro.ORMSupportClasses.SingleDecimalConverter', which is used instead.
Project File I/O::The typeconverter 'SD.LLBLGen.Pro.TypeConverters.SingleDecimalConverter' wasn't found, however a typeconverter with the same name in a different namespace was: 'SD.LLBLGen.Pro.ORMSupportClasses.SingleDecimalConverter', which is used instead.
Project File I/O::The typeconverter 'SD.LLBLGen.Pro.TypeConverters.SingleDecimalConverter' wasn't found, however a typeconverter with the same name in a different namespace was: 'SD.LLBLGen.Pro.ORMSupportClasses.SingleDecimalConverter', which is used instead.
Project File I/O::The typeconverter 'SD.LLBLGen.Pro.TypeConverters.SingleDecimalConverter' wasn't found, however a typeconverter with the same name in a different namespace was: 'SD.LLBLGen.Pro.ORMSupportClasses.SingleDecimalConverter', which is used instead.
Project File I/O::The typeconverter 'SD.LLBLGen.Pro.TypeConverters.SingleDecimalConverter' wasn't found, however a typeconverter with the same name in a different namespace was: 'SD.LLBLGen.Pro.ORMSupportClasses.SingleDecimalConverter', which is used instead.
Project File I/O::The typeconverter 'SD.LLBLGen.Pro.TypeConverters.SingleDecimalConverter' wasn't found, however a typeconverter with the same name in a different namespace was: 'SD.LLBLGen.Pro.ORMSupportClasses.SingleDecimalConverter', which is used instead.
Project File I/O::The typeconverter 'SD.LLBLGen.Pro.TypeConverters.SingleDecimalConverter' wasn't found, however a typeconverter with the same name in a different namespace was: 'SD.LLBLGen.Pro.ORMSupportClasses.SingleDecimalConverter', which is used instead.
Project File I/O::The typeconverter 'SD.LLBLGen.Pro.TypeConverters.SingleDecimalConverter' wasn't found, however a typeconverter with the same name in a different namespace was: 'SD.LLBLGen.Pro.ORMSupportClasses.SingleDecimalConverter', which is used instead.
Project File I/O::The typeconverter 'SD.LLBLGen.Pro.TypeConverters.SingleDecimalConverter' wasn't found, however a typeconverter with the same name in a different namespace was: 'SD.LLBLGen.Pro.ORMSupportClasses.SingleDecimalConverter', which is used instead.
Project File I/O::The typeconverter 'SD.LLBLGen.Pro.TypeConverters.Int32DecimalConverter' wasn't found, however a typeconverter with the same name in a different namespace was: 'SD.LLBLGen.Pro.ORMSupportClasses.Int32DecimalConverter', which is used instead.
Project File I/O::The typeconverter 'SD.LLBLGen.Pro.TypeConverters.SingleDecimalConverter' wasn't found, however a typeconverter with the same name in a different namespace was: 'SD.LLBLGen.Pro.ORMSupportClasses.SingleDecimalConverter', which is used instead.
Project File I/O::The typeconverter 'SD.LLBLGen.Pro.TypeConverters.SingleDecimalConverter' wasn't found, however a typeconverter with the same name in a different namespace was: 'SD.LLBLGen.Pro.ORMSupportClasses.SingleDecimalConverter', which is used instead.
Project File I/O::The typeconverter 'SD.LLBLGen.Pro.TypeConverters.SingleDecimalConverter' wasn't found, however a typeconverter with the same name in a different namespace was: 'SD.LLBLGen.Pro.ORMSupportClasses.SingleDecimalConverter', which is used instead.
Project File I/O::The typeconverter 'SD.LLBLGen.Pro.TypeConverters.Int32DecimalConverter' wasn't found, however a typeconverter with the same name in a different namespace was: 'SD.LLBLGen.Pro.ORMSupportClasses.Int32DecimalConverter', which is used instead.
Project File I/O::The typeconverter 'SD.LLBLGen.Pro.TypeConverters.SingleDecimalConverter' wasn't found, however a typeconverter with the same name in a different namespace was: 'SD.LLBLGen.Pro.ORMSupportClasses.SingleDecimalConverter', which is used instead.
Project File I/O::The typeconverter 'SD.LLBLGen.Pro.TypeConverters.SingleDecimalConverter' wasn't found, however a typeconverter with the same name in a different namespace was: 'SD.LLBLGen.Pro.ORMSupportClasses.SingleDecimalConverter', which is used instead.
Project File I/O::The typeconverter 'SD.LLBLGen.Pro.TypeConverters.SingleDecimalConverter' wasn't found, however a typeconverter with the same name in a different namespace was: 'SD.LLBLGen.Pro.ORMSupportClasses.SingleDecimalConverter', which is used instead.
Project File I/O::The typeconverter 'SD.LLBLGen.Pro.TypeConverters.SingleDecimalConverter' wasn't found, however a typeconverter with the same name in a different namespace was: 'SD.LLBLGen.Pro.ORMSupportClasses.SingleDecimalConverter', which is used instead.
Project File I/O::The typeconverter 'SD.LLBLGen.Pro.TypeConverters.SingleDecimalConverter' wasn't found, however a typeconverter with the same name in a different namespace was: 'SD.LLBLGen.Pro.ORMSupportClasses.SingleDecimalConverter', which is used instead.
Project File I/O::The typeconverter 'SD.LLBLGen.Pro.TypeConverters.SingleDecimalConverter' wasn't found, however a typeconverter with the same name in a different namespace was: 'SD.LLBLGen.Pro.ORMSupportClasses.SingleDecimalConverter', which is used instead.
Project File I/O::The typeconverter 'SD.LLBLGen.Pro.TypeConverters.SingleDecimalConverter' wasn't found, however a typeconverter with the same name in a different namespace was: 'SD.LLBLGen.Pro.ORMSupportClasses.SingleDecimalConverter', which is used instead.
Project File I/O::The typeconverter 'SD.LLBLGen.Pro.TypeConverters.SingleDecimalConverter' wasn't found, however a typeconverter with the same name in a different namespace was: 'SD.LLBLGen.Pro.ORMSupportClasses.SingleDecimalConverter', which is used instead.
Project File I/O::The typeconverter 'SD.LLBLGen.Pro.TypeConverters.SingleDecimalConverter' wasn't found, however a typeconverter with the same name in a different namespace was: 'SD.LLBLGen.Pro.ORMSupportClasses.SingleDecimalConverter', which is used instead.
Project File I/O::The typeconverter 'SD.LLBLGen.Pro.TypeConverters.SingleDecimalConverter' wasn't found, however a typeconverter with the same name in a different namespace was: 'SD.LLBLGen.Pro.ORMSupportClasses.SingleDecimalConverter', which is used instead.
Project File I/O::The typeconverter 'SD.LLBLGen.Pro.TypeConverters.SingleDecimalConverter' wasn't found, however a typeconverter with the same name in a different namespace was: 'SD.LLBLGen.Pro.ORMSupportClasses.SingleDecimalConverter', which is used instead.
Project File I/O::The typeconverter 'SD.LLBLGen.Pro.TypeConverters.SingleDecimalConverter' wasn't found, however a typeconverter with the same name in a different namespace was: 'SD.LLBLGen.Pro.ORMSupportClasses.SingleDecimalConverter', which is used instead.
Project File I/O::The typeconverter 'SD.LLBLGen.Pro.TypeConverters.Int32DecimalConverter' wasn't found, however a typeconverter with the same name in a different namespace was: 'SD.LLBLGen.Pro.ORMSupportClasses.Int32DecimalConverter', which is used instead.
Project File I/O::The typeconverter 'SD.LLBLGen.Pro.TypeConverters.Int32DecimalConverter' wasn't found, however a typeconverter with the same name in a different namespace was: 'SD.LLBLGen.Pro.ORMSupportClasses.Int32DecimalConverter', which is used instead.
Project File I/O::The typeconverter 'SD.LLBLGen.Pro.TypeConverters.Int32DecimalConverter' wasn't found, however a typeconverter with the same name in a different namespace was: 'SD.LLBLGen.Pro.ORMSupportClasses.Int32DecimalConverter', which is used instead.
Project File I/O::The typeconverter 'SD.LLBLGen.Pro.TypeConverters.Int32DecimalConverter' wasn't found, however a typeconverter with the same name in a different namespace was: 'SD.LLBLGen.Pro.ORMSupportClasses.Int32DecimalConverter', which is used instead.
Project File I/O::The typeconverter 'SD.LLBLGen.Pro.TypeConverters.Int32DecimalConverter' wasn't found, however a typeconverter with the same name in a different namespace was: 'SD.LLBLGen.Pro.ORMSupportClasses.Int32DecimalConverter', which is used instead.
Project File I/O::The typeconverter 'SD.LLBLGen.Pro.TypeConverters.Int32DecimalConverter' wasn't found, however a typeconverter with the same name in a different namespace was: 'SD.LLBLGen.Pro.ORMSupportClasses.Int32DecimalConverter', which is used instead.
Project File I/O::Project 'AQD' loaded successfully
Whereas if I load the designer first then load my project I don't get the errors.
Jeremy Thomas
VS 2017 C#, LLBLGen v5.4, Winforms, WPF and ASP.NET MVCLLBL & LinqPad
 
Top
daelmo
Support Team



Location:
Guatemala City
Joined on:
28-Nov-2005 23:35:24
Posted:
8150 posts
# Posted on: 09-May-2018 08:02:50.  
- Do you receive this every time?
- Does it happen with all projects or just that specific one?
- Do you have a small repro project to reproduce this or basic steps to reproduce the behavior?
- Please confirm that you are still using v5.2.7


David Elizondo
LLBLGen'ing (articles and code snippets) | linkedin | twitter
 
Top
TomDog
User



Location:
Wellington, New Zealand
Joined on:
25-Oct-2005 22:21:17
Posted:
570 posts
# Posted on: 31-Aug-2018 00:32:33.  
Slightly difference scenario but still:
  • Download <https://1drv.ms/u/s!ApSk-leF4Tiqi7QTFWM35N1Kff0WTw> (Copy URL between the brackets)
  • Extract DLLs from this zip to C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.X\Plugins (In my case X=4)
  • Download https://github.com/SolutionsDesign/LLBLGenProExamples_5.x/blob/master/Example_Authorization/LLBLGenPro%20Project/Authorization.llblgenproj
  • Open it in any v5 version (I used 5.4.3)
  • Add 'SD.LLBLGen.Pro.TypeConverters.DateTimeDateTimeUTCConverter' to Employees.BirthDate
  • Close and reopen project
  • Observe Employees.BirthDate still has the type converter
  • Close Designer
  • Open Authorization.llblgenproj by double clicking in explorer
  • Observe this error:
    Code:
    ---------------------------
    Reference to missing type converter found
    ---------------------------
    While loading the project the following type converter related error occured:

    A reference to the type converter 'SD.LLBLGen.Pro.TypeConverters.DateTimeDateTimeUTCConverter' was found, however this typeconverter wasn't loaded / found

    This is likely due to the project file referring to an additional type converter folder which either doesn't exist or doesn't contain a type converter dll with the type converter referenced. As a missing type converter results in all fields using the missing type converter having their types reset to string, LLBLGen Pro has aborted the project load.

    Do you want to specify the additional type converter folder for this project and retry? Click 'Yes' if you do, otherwise click 'No' to abort the load action. Be aware that the selected folder will be set as 'AdditionalTypeConverterFolder' in the project properties of this project, so you should save the project after it's successfully loaded.
    ---------------------------
    Yes No
    ---------------------------

  • Project hasn't loaded but this is on the log
    Code:
    Project File I/O::A reference to the type converter 'SD.LLBLGen.Pro.TypeConverters.DateTimeDateTimeUTCConverter' was found, however this typeconverter wasn't loaded / found
    BEFORE
    TypeConverterLoader::Successfully instantiated type converter 'SD.LLBLGen.Pro.TypeConverters.DateTimeDateTimeUTCConverter' from assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\TypeConverters\SD.LLBLGen.Pro.TypeConverters.dll'.
Jeremy Thomas
VS 2017 C#, LLBLGen v5.4, Winforms, WPF and ASP.NET MVCLLBL & LinqPad
 
Top
Walaa
Support Team



Location:

Joined on:
21-Aug-2005 16:03:48
Posted:
14639 posts
# Posted on: 31-Aug-2018 10:52:52.  
I followed the same steps, and I can't reproduce it, using v.5.4.0
The file opens successfully without errors, when double clicking on it, and the TypeConverter assignment is still there.


  Top
TomDog
User



Location:
Wellington, New Zealand
Joined on:
25-Oct-2005 22:21:17
Posted:
570 posts
# Posted on: 31-Aug-2018 12:08:47.  
Found the trigger, I have a LLBL plugin which references Microsoft.CodeAnalysis.CSharp.dll and Microsoft.CodeAnalysis.CSharp.Scripting. If those two assemblies are present in the plugin directory I get these message in the log
Code:
DatabaseDriverStore::Successfully loaded driver 'SQL Server Driver (SqlClient)' from 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Drivers\SqlServer\SD.LLBLGen.Pro.DBDrivers.SqlServerDBDriver.dll'
PluginStore::Error loading potential plug-in assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Plugins\Microsoft.CodeAnalysis.CSharp.dll': One or more dependencies couldn't be resolved. Plug-ins in this assembly will be unavailable.
PluginStore::Error loading potential plug-in assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Plugins\Microsoft.CodeAnalysis.CSharp.Scripting.dll': One or more dependencies couldn't be resolved. Plug-ins in this assembly will be unavailable.
PluginStore::Error loading potential plug-in assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Plugins\Microsoft.CodeAnalysis.dll': One or more dependencies couldn't be resolved. Plug-ins in this assembly will be unavailable.
PluginStore::Error loading potential plug-in assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Plugins\Microsoft.CodeAnalysis.Scripting.dll': One or more dependencies couldn't be resolved. Plug-ins in this assembly will be unavailable.
PluginStore::Successfully loaded plug-in 'Add Custom Properties Plug-in' from assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Plugins\SD.LLBLGen.Pro.Plugins.dll'.
PluginStore::Successfully loaded plug-in 'Plural to Singular converter plug-in' from assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Plugins\SD.LLBLGen.Pro.Plugins.dll'.
PluginStore::Successfully loaded plug-in 'Singular to Plural converter plug-in' from assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Plugins\SD.LLBLGen.Pro.Plugins.dll'.
PluginStore::Successfully loaded plug-in 'Project Inspector Plug-in' from assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Plugins\SD.LLBLGen.Pro.Plugins.dll'.
PluginStore::Error loading potential importer plug-in assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Plugins\Microsoft.CodeAnalysis.CSharp.dll': One or more dependencies couldn't be resolved. Importer plug-ins in this assembly will be unavailable.
PluginStore::Error loading potential importer plug-in assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Plugins\Microsoft.CodeAnalysis.CSharp.Scripting.dll': One or more dependencies couldn't be resolved. Importer plug-ins in this assembly will be unavailable.
Project File I/O::A reference to the type converter 'SD.LLBLGen.Pro.TypeConverters.DateTimeDateTimeUTCConverter' was found, however this typeconverter wasn't loaded / found
PluginStore::Error loading potential importer plug-in assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Plugins\Microsoft.CodeAnalysis.dll': One or more dependencies couldn't be resolved. Importer plug-ins in this assembly will be unavailable.
PluginStore::Error loading potential importer plug-in assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Plugins\Microsoft.CodeAnalysis.Scripting.dll': One or more dependencies couldn't be resolved. Importer plug-ins in this assembly will be unavailable.
ImporterStore::Successfully loaded importer plug-in 'LLBLGen Pro project importer' from assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Plugins\SD.LLBLGen.Pro.Importers.dll'.
ImporterStore::Successfully loaded importer plug-in 'EntityFramework EDMX importer' from assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Plugins\SD.LLBLGen.Pro.Importers.dll'.
TypeConverterLoader::Successfully instantiated type converter 'SD.LLBLGen.Pro.TypeConverters.BooleanNumericConverter' from assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\TypeConverters\SD.LLBLGen.Pro.TypeConverters.dll'.
If I remove those two files then the project loads. I'm guessing some sort of timing issue.
Jeremy Thomas
VS 2017 C#, LLBLGen v5.4, Winforms, WPF and ASP.NET MVCLLBL & LinqPad
 
Top
Otis
LLBLGen Pro Team



Location:
The Hague, The Netherlands
Joined on:
17-Aug-2003 18:00:36
Posted:
38090 posts
# Posted on: 31-Aug-2018 12:46:25.  
I don't see how the failed probe for plugins on those dlls makes the project fail to load. Those messages are harmless, but a project that doesn't load is a problem.

So I'm a bit confused what the two have to do with each other: the project that fails to load and the messages in the log...


Frans Bouma
LLBLGen Pro / ORM Profiler Lead Developer | Blog | Twitter
 
Top
TomDog
User



Location:
Wellington, New Zealand
Joined on:
25-Oct-2005 22:21:17
Posted:
570 posts
# Posted on: 03-Sep-2018 13:32:34.  
I've managed to repro on two other machines with updated steps above and hopefully you can too.
Jeremy Thomas
VS 2017 C#, LLBLGen v5.4, Winforms, WPF and ASP.NET MVCLLBL & LinqPad
 
Top
Otis
LLBLGen Pro Team



Location:
The Hague, The Netherlands
Joined on:
17-Aug-2003 18:00:36
Posted:
38090 posts
# Posted on: 03-Sep-2018 13:49:58.  
TomDog wrote:
I've managed to repro on two other machines with updated steps above and hopefully you can too.

Please be *very* specific which post you're referring to, which steps and what exactly goes wrong.

you mean this post? https://www.llblgen.com/tinyforum/GotoMessage.aspx?MessageID=141922&ThreadID=24663


Frans Bouma
LLBLGen Pro / ORM Profiler Lead Developer | Blog | Twitter
 
Top
TomDog
User



Location:
Wellington, New Zealand
Joined on:
25-Oct-2005 22:21:17
Posted:
570 posts
# Posted on: 03-Sep-2018 14:18:17.  
OK, yes that post with all those steps
Jeremy Thomas
VS 2017 C#, LLBLGen v5.4, Winforms, WPF and ASP.NET MVCLLBL & LinqPad
 
Top
Otis
LLBLGen Pro Team



Location:
The Hague, The Netherlands
Joined on:
17-Aug-2003 18:00:36
Posted:
38090 posts
# Posted on: 03-Sep-2018 14:37:53.  
TomDog wrote:
OK, yes that post with all those steps

Can't repro it. The crucial step I can't do is the 'double click' action as it's assigned with v4.2's designer. Are you sure it opens 5.4.3 when double clicking?

Just closing the designer and reopening it in the designer again and again still works.

I'll see if I can uninstall some versions and install 5.4.3 and retry with the release build.



Frans Bouma
LLBLGen Pro / ORM Profiler Lead Developer | Blog | Twitter
 
Top
Otis
LLBLGen Pro Team



Location:
The Hague, The Netherlands
Joined on:
17-Aug-2003 18:00:36
Posted:
38090 posts
# Posted on: 03-Sep-2018 14:44:50.  
Nope, works fine...

Double clicking the file to load it into v5.4.3, type converter is still there... as are the plugin probe errors on the dlls without plugins, which is expected.

Be sure that you don't have multiple designers installed and double clicking the llblgenproj file loads in the right designer version... Opening the designer and then loading the project should do the same thing tho, so if that fails again (I doubt it as the steps include this already which succeeds) then something's off...
Frans Bouma
LLBLGen Pro / ORM Profiler Lead Developer | Blog | Twitter
 
Top
TomDog
User



Location:
Wellington, New Zealand
Joined on:
25-Oct-2005 22:21:17
Posted:
570 posts
# Posted on: 04-Sep-2018 08:34:49.  
I just tried it on a machine with no dev tools on it.
I installed LLBL V5.4.2 then went through the steps and it error-ed as described.


Jeremy Thomas
VS 2017 C#, LLBLGen v5.4, Winforms, WPF and ASP.NET MVCLLBL & LinqPad
 
Top
Otis
LLBLGen Pro Team



Location:
The Hague, The Netherlands
Joined on:
17-Aug-2003 18:00:36
Posted:
38090 posts
# Posted on: 04-Sep-2018 09:02:12.  
TomDog wrote:
I just tried it on a machine with no dev tools on it.
I installed LLBL V5.4.2 then went through the steps and it error-ed as described.

well, I can't reproduce it here so I can't see what's wrong. But I asked you a question, whether it occurs again if you reload the project again by closing the designer, opening it again and then load the project through 'open project' and not through double clicking the file.
Frans Bouma
LLBLGen Pro / ORM Profiler Lead Developer | Blog | Twitter
 
Top
TomDog
User



Location:
Wellington, New Zealand
Joined on:
25-Oct-2005 22:21:17
Posted:
570 posts
# Posted on: 04-Sep-2018 09:06:46.  
I never get an error when opening designer first, only when double clicking the file

Jeremy Thomas
VS 2017 C#, LLBLGen v5.4, Winforms, WPF and ASP.NET MVCLLBL & LinqPad
 
Top
Otis
LLBLGen Pro Team



Location:
The Hague, The Netherlands
Joined on:
17-Aug-2003 18:00:36
Posted:
38090 posts
# Posted on: 04-Sep-2018 09:32:50.  
TomDog wrote:
I never get an error when opening designer first, only when double clicking the file

then the file association is wrong somewhere. I can't reproduce it with a freshly installed designer. And if I can't repro it I can't fix anything...

If you open an elevated command prompt and type:
ftype
you'll get a list of all filetypes with the associated program. You'll see with llblgen pro it simply opens the exe and passes the file as the first argument. Is 'llblgenproj' associated with the right designer?
Frans Bouma
LLBLGen Pro / ORM Profiler Lead Developer | Blog | Twitter
 
Top
TomDog
User



Location:
Wellington, New Zealand
Joined on:
25-Oct-2005 22:21:17
Posted:
570 posts
# Posted on: 04-Sep-2018 09:43:45.  
On this clean machine I only have one designer and ftype looks like I would expect.

I could repro on a Azure VM then give you access if that would help.


Jeremy Thomas
VS 2017 C#, LLBLGen v5.4, Winforms, WPF and ASP.NET MVCLLBL & LinqPad
 
Top
Otis
LLBLGen Pro Team



Location:
The Hague, The Netherlands
Joined on:
17-Aug-2003 18:00:36
Posted:
38090 posts
# Posted on: 04-Sep-2018 10:29:22.  
TomDog wrote:
On this clean machine I only have one designer and ftype looks like I would expect.

I could repro on a Azure VM then give you access if that would help.

That wouldn't help as I can't debug it if it happens... So you have to give as specific answers as possible, I'm afraid, to get to the bottom of this...

if you on the command line specify:
<llblgenpro installer path>\llblgenpro.exe <project file>

it then doesn't work as well?

I suspect an exception somewhere but I fail to see why this occurs only sometimes... (exception as in: it terminates probing and therefore misses the type converter). So could you copy/paste the complete log in the application output here and check if the type converter is indeed loaded in Tools -> View Loaded External Types ?
Frans Bouma
LLBLGen Pro / ORM Profiler Lead Developer | Blog | Twitter
 
Top
TomDog
User



Location:
Wellington, New Zealand
Joined on:
25-Oct-2005 22:21:17
Posted:
570 posts
# Posted on: 04-Sep-2018 11:30:51.  
Running
Code:
"C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\LLBLGenPro.exe" "C:\Users\jerem\Documents\LLBLGen Pro\v5.4\Projects\AuthorizationTC.llblgenproj"
gives
Code:
DatabaseDriverStore::Successfully loaded driver 'MS Access Driver (OleDb)' from 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Drivers\Access\SD.LLBLGen.Pro.DBDrivers.AccessDBDriver.dll'
DatabaseDriverStore::Successfully loaded driver 'IBM DB2 UDB Driver (IBM DB2 .NET)' from 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Drivers\DB2\SD.LLBLGen.Pro.DBDrivers.DB2DBDriver.dll'
DatabaseDriverStore::Successfully loaded driver 'Firebird Driver (Firebird.NET)' from 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Drivers\Firebird\SD.LLBLGen.Pro.DBDrivers.FirebirdDBDriver.dll'
DatabaseDriverStore::Successfully loaded driver 'MySql Driver (MySQLDirect)' from 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Drivers\MySql\SD.LLBLGen.Pro.DBDrivers.MySqlDBDriver.dll'
DatabaseDriverStore::Successfully loaded driver 'Oracle Driver (MS Oracle)' from 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Drivers\OracleMSOracle\SD.LLBLGen.Pro.DBDrivers.OracleDBDriver_MSOracle.dll'
DatabaseDriverStore::Successfully loaded driver 'Oracle Driver (ODP.NET)' from 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Drivers\OracleODPNET\SD.LLBLGen.Pro.DBDrivers.OracleDBDriver_ODPNET.dll'
DatabaseDriverStore::Successfully loaded driver 'PostgreSql Driver (Npgsql)' from 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Drivers\PostgreSql\SD.LLBLGen.Pro.DBDrivers.PostgreSqlDBDriver.dll'
DatabaseDriverStore::Successfully loaded driver 'SQL Server Driver (SqlClient)' from 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Drivers\SqlServer\SD.LLBLGen.Pro.DBDrivers.SqlServerDBDriver.dll'
PluginStore::Error loading potential plug-in assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Plugins\Microsoft.CodeAnalysis.CSharp.dll': One or more dependencies couldn't be resolved. Plug-ins in this assembly will be unavailable.
PluginStore::Error loading potential plug-in assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Plugins\Microsoft.CodeAnalysis.CSharp.Scripting.dll': One or more dependencies couldn't be resolved. Plug-ins in this assembly will be unavailable.
PluginStore::Error loading potential plug-in assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Plugins\Microsoft.CodeAnalysis.dll': One or more dependencies couldn't be resolved. Plug-ins in this assembly will be unavailable.
PluginStore::Error loading potential plug-in assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Plugins\Microsoft.CodeAnalysis.Scripting.dll': One or more dependencies couldn't be resolved. Plug-ins in this assembly will be unavailable.
PluginStore::Error loading potential plug-in assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Plugins\Microsoft.ReportViewer.DataVisualization.dll': One or more dependencies couldn't be resolved. Plug-ins in this assembly will be unavailable.
PluginStore::Successfully loaded plug-in 'Add Custom Properties Plug-in' from assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Plugins\SD.LLBLGen.Pro.Plugins.dll'.
PluginStore::Successfully loaded plug-in 'Plural to Singular converter plug-in' from assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Plugins\SD.LLBLGen.Pro.Plugins.dll'.
PluginStore::Successfully loaded plug-in 'Singular to Plural converter plug-in' from assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Plugins\SD.LLBLGen.Pro.Plugins.dll'.
PluginStore::Successfully loaded plug-in 'Project Inspector Plug-in' from assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Plugins\SD.LLBLGen.Pro.Plugins.dll'.
Project File I/O::A reference to the type converter 'SD.LLBLGen.Pro.TypeConverters.DateTimeDateTimeUTCConverter' was found, however this typeconverter wasn't loaded / found
PluginStore::Error loading potential importer plug-in assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Plugins\Microsoft.CodeAnalysis.CSharp.dll': One or more dependencies couldn't be resolved. Importer plug-ins in this assembly will be unavailable.
PluginStore::Error loading potential importer plug-in assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Plugins\Microsoft.CodeAnalysis.CSharp.Scripting.dll': One or more dependencies couldn't be resolved. Importer plug-ins in this assembly will be unavailable.
PluginStore::Error loading potential importer plug-in assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Plugins\Microsoft.CodeAnalysis.dll': One or more dependencies couldn't be resolved. Importer plug-ins in this assembly will be unavailable.
PluginStore::Error loading potential importer plug-in assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Plugins\Microsoft.CodeAnalysis.Scripting.dll': One or more dependencies couldn't be resolved. Importer plug-ins in this assembly will be unavailable.
PluginStore::Error loading potential importer plug-in assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Plugins\Microsoft.ReportViewer.DataVisualization.dll': One or more dependencies couldn't be resolved. Importer plug-ins in this assembly will be unavailable.
ImporterStore::Successfully loaded importer plug-in 'LLBLGen Pro project importer' from assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Plugins\SD.LLBLGen.Pro.Importers.dll'.
ImporterStore::Successfully loaded importer plug-in 'EntityFramework EDMX importer' from assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Plugins\SD.LLBLGen.Pro.Importers.dll'.
TypeConverterLoader::Successfully instantiated type converter 'SD.LLBLGen.Pro.TypeConverters.BooleanNumericConverter' from assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\TypeConverters\SD.LLBLGen.Pro.TypeConverters.dll'.
TypeConverterLoader::Successfully instantiated type converter 'SD.LLBLGen.Pro.TypeConverters.BooleanCharYNConverter' from assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\TypeConverters\SD.LLBLGen.Pro.TypeConverters.dll'.
TypeConverterLoader::Successfully instantiated type converter 'SD.LLBLGen.Pro.TypeConverters.ByteDecimalConverter' from assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\TypeConverters\SD.LLBLGen.Pro.TypeConverters.dll'.
TypeConverterLoader::Successfully instantiated type converter 'SD.LLBLGen.Pro.TypeConverters.CharStringConverter' from assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\TypeConverters\SD.LLBLGen.Pro.TypeConverters.dll'.
TypeConverterLoader::Successfully instantiated type converter 'SD.LLBLGen.Pro.TypeConverters.DateTimeDateTimeUTCConverter' from assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\TypeConverters\SD.LLBLGen.Pro.TypeConverters.dll'.
TypeConverterLoader::Successfully instantiated type converter 'SD.LLBLGen.Pro.TypeConverters.GuidByteArrayConverter' from assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\TypeConverters\SD.LLBLGen.Pro.TypeConverters.dll'.
TypeConverterLoader::Successfully instantiated type converter 'SD.LLBLGen.Pro.TypeConverters.GuidStringConverter' from assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\TypeConverters\SD.LLBLGen.Pro.TypeConverters.dll'.
TypeConverterLoader::Successfully instantiated type converter 'SD.LLBLGen.Pro.TypeConverters.DoubleDecimalConverter' from assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\TypeConverters\SD.LLBLGen.Pro.TypeConverters.dll'.
TypeConverterLoader::Successfully instantiated type converter 'SD.LLBLGen.Pro.TypeConverters.SingleDecimalConverter' from assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\TypeConverters\SD.LLBLGen.Pro.TypeConverters.dll'.
TypeConverterLoader::Successfully instantiated type converter 'SD.LLBLGen.Pro.TypeConverters.Int64DecimalConverter' from assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\TypeConverters\SD.LLBLGen.Pro.TypeConverters.dll'.
TypeConverterLoader::Successfully instantiated type converter 'SD.LLBLGen.Pro.TypeConverters.Int32DecimalConverter' from assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\TypeConverters\SD.LLBLGen.Pro.TypeConverters.dll'.
TypeConverterLoader::Successfully instantiated type converter 'SD.LLBLGen.Pro.TypeConverters.Int16DecimalConverter' from assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\TypeConverters\SD.LLBLGen.Pro.TypeConverters.dll'.
System::Initialization done. Ready.
System::Done
DateTimeDateTimeUTCConverter shows up in list, at which point I can then load the project.
By comparison this is the log opening designer first
Code:
DatabaseDriverStore::Successfully loaded driver 'MS Access Driver (OleDb)' from 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Drivers\Access\SD.LLBLGen.Pro.DBDrivers.AccessDBDriver.dll'
DatabaseDriverStore::Successfully loaded driver 'IBM DB2 UDB Driver (IBM DB2 .NET)' from 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Drivers\DB2\SD.LLBLGen.Pro.DBDrivers.DB2DBDriver.dll'
DatabaseDriverStore::Successfully loaded driver 'Firebird Driver (Firebird.NET)' from 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Drivers\Firebird\SD.LLBLGen.Pro.DBDrivers.FirebirdDBDriver.dll'
DatabaseDriverStore::Successfully loaded driver 'MySql Driver (MySQLDirect)' from 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Drivers\MySql\SD.LLBLGen.Pro.DBDrivers.MySqlDBDriver.dll'
DatabaseDriverStore::Successfully loaded driver 'Oracle Driver (MS Oracle)' from 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Drivers\OracleMSOracle\SD.LLBLGen.Pro.DBDrivers.OracleDBDriver_MSOracle.dll'
DatabaseDriverStore::Successfully loaded driver 'Oracle Driver (ODP.NET)' from 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Drivers\OracleODPNET\SD.LLBLGen.Pro.DBDrivers.OracleDBDriver_ODPNET.dll'
DatabaseDriverStore::Successfully loaded driver 'PostgreSql Driver (Npgsql)' from 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Drivers\PostgreSql\SD.LLBLGen.Pro.DBDrivers.PostgreSqlDBDriver.dll'
DatabaseDriverStore::Successfully loaded driver 'SQL Server Driver (SqlClient)' from 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Drivers\SqlServer\SD.LLBLGen.Pro.DBDrivers.SqlServerDBDriver.dll'
PluginStore::Error loading potential plug-in assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Plugins\Microsoft.CodeAnalysis.CSharp.dll': One or more dependencies couldn't be resolved. Plug-ins in this assembly will be unavailable.
PluginStore::Error loading potential plug-in assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Plugins\Microsoft.CodeAnalysis.CSharp.Scripting.dll': One or more dependencies couldn't be resolved. Plug-ins in this assembly will be unavailable.
PluginStore::Error loading potential plug-in assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Plugins\Microsoft.CodeAnalysis.dll': One or more dependencies couldn't be resolved. Plug-ins in this assembly will be unavailable.
PluginStore::Error loading potential plug-in assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Plugins\Microsoft.CodeAnalysis.Scripting.dll': One or more dependencies couldn't be resolved. Plug-ins in this assembly will be unavailable.
PluginStore::Error loading potential plug-in assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Plugins\Microsoft.ReportViewer.DataVisualization.dll': One or more dependencies couldn't be resolved. Plug-ins in this assembly will be unavailable.
PluginStore::Successfully loaded plug-in 'Add Custom Properties Plug-in' from assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Plugins\SD.LLBLGen.Pro.Plugins.dll'.
PluginStore::Successfully loaded plug-in 'Plural to Singular converter plug-in' from assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Plugins\SD.LLBLGen.Pro.Plugins.dll'.
PluginStore::Successfully loaded plug-in 'Singular to Plural converter plug-in' from assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Plugins\SD.LLBLGen.Pro.Plugins.dll'.
PluginStore::Successfully loaded plug-in 'Project Inspector Plug-in' from assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Plugins\SD.LLBLGen.Pro.Plugins.dll'.
PluginStore::Error loading potential importer plug-in assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Plugins\Microsoft.CodeAnalysis.CSharp.dll': One or more dependencies couldn't be resolved. Importer plug-ins in this assembly will be unavailable.
PluginStore::Error loading potential importer plug-in assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Plugins\Microsoft.CodeAnalysis.CSharp.Scripting.dll': One or more dependencies couldn't be resolved. Importer plug-ins in this assembly will be unavailable.
PluginStore::Error loading potential importer plug-in assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Plugins\Microsoft.CodeAnalysis.dll': One or more dependencies couldn't be resolved. Importer plug-ins in this assembly will be unavailable.
PluginStore::Error loading potential importer plug-in assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Plugins\Microsoft.CodeAnalysis.Scripting.dll': One or more dependencies couldn't be resolved. Importer plug-ins in this assembly will be unavailable.
PluginStore::Error loading potential importer plug-in assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Plugins\Microsoft.ReportViewer.DataVisualization.dll': One or more dependencies couldn't be resolved. Importer plug-ins in this assembly will be unavailable.
ImporterStore::Successfully loaded importer plug-in 'LLBLGen Pro project importer' from assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Plugins\SD.LLBLGen.Pro.Importers.dll'.
ImporterStore::Successfully loaded importer plug-in 'EntityFramework EDMX importer' from assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\Plugins\SD.LLBLGen.Pro.Importers.dll'.
TypeConverterLoader::Successfully instantiated type converter 'SD.LLBLGen.Pro.TypeConverters.BooleanNumericConverter' from assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\TypeConverters\SD.LLBLGen.Pro.TypeConverters.dll'.
TypeConverterLoader::Successfully instantiated type converter 'SD.LLBLGen.Pro.TypeConverters.BooleanCharYNConverter' from assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\TypeConverters\SD.LLBLGen.Pro.TypeConverters.dll'.
TypeConverterLoader::Successfully instantiated type converter 'SD.LLBLGen.Pro.TypeConverters.ByteDecimalConverter' from assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\TypeConverters\SD.LLBLGen.Pro.TypeConverters.dll'.
TypeConverterLoader::Successfully instantiated type converter 'SD.LLBLGen.Pro.TypeConverters.CharStringConverter' from assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\TypeConverters\SD.LLBLGen.Pro.TypeConverters.dll'.
TypeConverterLoader::Successfully instantiated type converter 'SD.LLBLGen.Pro.TypeConverters.DateTimeDateTimeUTCConverter' from assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\TypeConverters\SD.LLBLGen.Pro.TypeConverters.dll'.
TypeConverterLoader::Successfully instantiated type converter 'SD.LLBLGen.Pro.TypeConverters.GuidByteArrayConverter' from assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\TypeConverters\SD.LLBLGen.Pro.TypeConverters.dll'.
TypeConverterLoader::Successfully instantiated type converter 'SD.LLBLGen.Pro.TypeConverters.GuidStringConverter' from assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\TypeConverters\SD.LLBLGen.Pro.TypeConverters.dll'.
TypeConverterLoader::Successfully instantiated type converter 'SD.LLBLGen.Pro.TypeConverters.DoubleDecimalConverter' from assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\TypeConverters\SD.LLBLGen.Pro.TypeConverters.dll'.
TypeConverterLoader::Successfully instantiated type converter 'SD.LLBLGen.Pro.TypeConverters.SingleDecimalConverter' from assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\TypeConverters\SD.LLBLGen.Pro.TypeConverters.dll'.
TypeConverterLoader::Successfully instantiated type converter 'SD.LLBLGen.Pro.TypeConverters.Int64DecimalConverter' from assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\TypeConverters\SD.LLBLGen.Pro.TypeConverters.dll'.
TypeConverterLoader::Successfully instantiated type converter 'SD.LLBLGen.Pro.TypeConverters.Int32DecimalConverter' from assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\TypeConverters\SD.LLBLGen.Pro.TypeConverters.dll'.
TypeConverterLoader::Successfully instantiated type converter 'SD.LLBLGen.Pro.TypeConverters.Int16DecimalConverter' from assembly file 'C:\Program Files (x86)\Solutions Design\LLBLGen Pro v5.4\TypeConverters\SD.LLBLGen.Pro.TypeConverters.dll'.
System::Done
System::Initialization done. Ready.
then project
Code:
Project File I/O::Project 'Authorization' loaded successfully


Jeremy Thomas
VS 2017 C#, LLBLGen v5.4, Winforms, WPF and ASP.NET MVCLLBL & LinqPad
 
Top
Otis
LLBLGen Pro Team



Location:
The Hague, The Netherlands
Joined on:
17-Aug-2003 18:00:36
Posted:
38090 posts
# Posted on: 04-Sep-2018 13:23:34.  
Thanks, that suggests a timing issue indeed: the general stuff is still loading when the project is loaded through the argument passed to the exe and therefore it's missed.

I hope there's a solution for this, but not sure there is, to be honest. It's also a bit of a pain to reproduce it if everything works here...
Frans Bouma
LLBLGen Pro / ORM Profiler Lead Developer | Blog | Twitter
 
Top
Pages: 1 2  


Powered by HnD ©2002-2007 Solutions Design
HnD uses LLBLGen Pro

Version: 2.1.12172008 Final.