Home
Help
Register
Log in

Search

 
   Active Threads  

You are here: Home > LLBLGen Pro > Bugs & Issues> Initial install of 5.6
 

Pages: 1
Bugs & Issues
Initial install of 5.6
Page:1/1 

  Print all messages in this thread  
Poster Message
timothyleerussell
User



Location:

Joined on:
02-Oct-2008 07:48:55
Posted:
25 posts
# Posted on: 23-Aug-2019 22:34:15.  
I'm getting this message on first launch of the standalone designer after installation.

Second and subsequent launches seem to be fine.

Thanks,
Timothy



Exception information.
=============================================================
LLBLGen Pro version: v5.6. Build: 5.6.0

Exception details:
=====================
Message: Object is currently in use elsewhere.
Source: System.Drawing
Stack trace:
at System.Drawing.Graphics.get_PageUnit()
at DevExpress.Utils.Text.FontsCache.GetFontCacheByFont(Graphics graphics, Font font)
at DevExpress.Utils.Text.TextUtils.GetStringSize(Graphics g, String text, Font font, StringFormat stringFormat, Int32 maxWidth, Int32 maxHeight, IWordBreakProvider wordBreakProvider, Boolean& isCropped)
at DevExpress.Utils.Paint.XPaintMixed.CalcTextSize(Graphics g, String s, Font font, StringFormat strFormat, Int32 maxWidth, Int32 maxHeight, Boolean& isCropped)
at DevExpress.XtraEditors.ViewInfo.LabelControlViewInfo.CalcSimpleTextSize(String Text, Boolean useHotkeyPrefix, LabelAutoSizeMode mode, Int32 predWidth, Int32 predHeight)
at DevExpress.XtraEditors.ViewInfo.LabelControlViewInfo.CalcTextSize(String Text, Boolean useHotkeyPrefix, LabelAutoSizeMode mode, Int32 predWidth, Int32 predHeight)
at DevExpress.XtraEditors.LabelControl.GetPreferredSize(Size proposedSize)
at DevExpress.XtraEditors.LabelControl.SetBoundsCore(Int32 x, Int32 y, Int32 width, Int32 height, BoundsSpecified specified)
at System.Windows.Forms.Control.System.Windows.Forms.Layout.IArrangedElement.SetBounds(Rectangle bounds, BoundsSpecified specified)
at System.Windows.Forms.Layout.CommonProperties.SetAutoSize(IArrangedElement element, Boolean value)
at System.Windows.Forms.Control.set_AutoSize(Boolean value)
at DevExpress.XtraEditors.LabelControl.set_AutoSizeMode(LabelAutoSizeMode value)
at SD.LLBLGen.Pro.Gui.Controls.NotePanel.InitializeComponent()
at SD.LLBLGen.Pro.Gui.Forms.SimpleExceptionViewer.InitializeComponent()
at SD.LLBLGen.Pro.Gui.Forms.SimpleExceptionViewer..ctor(Exception toView, String caption)
at SD.LLBLGen.Pro.Gui.Forms.SimpleExceptionViewer.Show(IWin32Window parent, Exception toView, String caption)
at SD.LLBLGen.Pro.Gui.Program.DoApplicationStart(String appStartPath, String fileToLoad, Boolean startedFromVSNet)
at SD.LLBLGen.Pro.Gui.Program.Main(String[] args)

Inner exception: <null>
  Top
Otis
LLBLGen Pro Team



Location:
The Hague, The Netherlands
Joined on:
17-Aug-2003 18:00:36
Posted:
37476 posts
# Posted on: 24-Aug-2019 10:09:51.  
We've seen this sporadically and it appears to be skin definition related and a bug in devexpress' controls. We had a workaround to stop this, but apparently this isn't the case. We'll see if we can reproduce it again, it's a bit cumbersome to reproduce as it doesn't happen very often... (for instance we haven't seen this issue pop up for 2 months now)

Did you start the designer by double clicking an llblgenproj file? Is there anything unusual with your windows setup, like you're using RDP into a virtual machine?


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:
37476 posts
# Posted on: 25-Aug-2019 15:58:22.  
It doesn't look like it's the one we had and fixed: it looks like you got an initial error somewhere, that was about to be displayed and *that* triggered the error you ran into. We have a multi-threaded startup process and it's likely this particular situation breaks out of the syncing we've setup so we need to track down where the initial error might have occurred and then try to trigger it and see if that reproduces this particular situation.

We can't otherwise reproduce it, tried it on several machines.
Frans Bouma
LLBLGen Pro / ORM Profiler Lead Developer | Blog | Twitter
 
Top
timothyleerussell
User



Location:

Joined on:
02-Oct-2008 07:48:55
Posted:
25 posts
# Posted on: 26-Aug-2019 02:22:30.  
Ok, thanks...it's not really affecting me as it only did it that one time...but I thought you'd like to know.

I am not doing anything out of the ordinary really -- I do have probably 5 versions of LLBLGen installed but I assume they stay in their sandbox. I'm using Win10 latest, multi-mon support off a CalDigit dock from a year-old Zenbook Pro i9.

The only thing I could think of is that maybe it imported settings from the previous version or something which had an issue getting re-hydrated until the oob-state persisted its (now corrected) default settings on the first close?


  Top
Otis
LLBLGen Pro Team



Location:
The Hague, The Netherlands
Joined on:
17-Aug-2003 18:00:36
Posted:
37476 posts
# Posted on: 26-Aug-2019 09:43:56.  
yeah we think it's an initial error in the work that's being done at startup, that led to an exception to be displayed but that failed as the dialog is on another thread and that caused the font object inside devexpress' controls to throw up (it shouldn't, but alas... ) and cause this (looking at the stacktrace).

I do think you did see the startup dialog appearing and then got this exception, correct?

So it shouldn't happen again (and we'll try to not make it happen for others as well Regular Smiley ) Thanks for reporting Regular Smiley
Frans Bouma
LLBLGen Pro / ORM Profiler Lead Developer | Blog | Twitter
 
Top
ewe
User



Location:

Joined on:
06-Sep-2013 21:06:15
Posted:
3 posts
# Posted on: 26-Aug-2019 23:08:22.  
I upgraded from 5.2->5.6.

On the first solution I am trying, I am getting over a hundred errors saying the name "DynamicRelation" could not be found. They are not found in the     public partial class EntityFactoryBase2<TEntity> : EntityFactoryCore2 class.

The ModelInfoProviderSingleton is not found in the FieldCreationClasses.

Am I missing a library? The class only has one using other than System. It is ORMSupportClasses. I have that referenced in the project.

Please advise.

Thanks.








  Top
Otis
LLBLGen Pro Team



Location:
The Hague, The Netherlands
Joined on:
17-Aug-2003 18:00:36
Posted:
37476 posts
# Posted on: 27-Aug-2019 08:59:49.  
Be sure you're referencing the right ORMSupport Classes package (i.e. v5.6). We recommend to use nuget for this, so you can easily upgrade when we upload a patch version.

It might be you did reference the new dll but vs still loads the old one. Please check this in the properties pane of visual studio
Frans Bouma
LLBLGen Pro / ORM Profiler Lead Developer | Blog | Twitter
 
Top
ewe
User



Location:

Joined on:
06-Sep-2013 21:06:15
Posted:
3 posts
# Posted on: 27-Aug-2019 15:37:17.  
I deleted the two existing projects, and regenerated them from scratch rather than updating. I copied over my extensions to Entity and TypedView classes into new extension folders, and then rebuilt. All of the errors went away. I will try this with my various other LLB gen projects and hopefully can make some progress.

Thanks for the quick response.


  Top
timothyleerussell
User



Location:

Joined on:
02-Oct-2008 07:48:55
Posted:
25 posts
# Posted on: 27-Aug-2019 19:36:40.  
Just as a follow up, I reinstalled 5.6 because I just installed VS 2019 (been waiting for some extensions I need to catch up) and it seemed like an easy way to get the LLBLGen 2019 extension installed.

When I launched the standalone editor for the first time after reinstalling, I got the error again on first launch but not on subsequent launches.

Don't need a reply, just more info for you.

Thanks!
Timothy
  Top
Otis
LLBLGen Pro Team



Location:
The Hague, The Netherlands
Joined on:
17-Aug-2003 18:00:36
Posted:
37476 posts
# Posted on: 27-Aug-2019 22:29:04.  
ewe wrote:
I deleted the two existing projects, and regenerated them from scratch rather than updating. I copied over my extensions to Entity and TypedView classes into new extension folders, and then rebuilt. All of the errors went away. I will try this with my various other LLB gen projects and hopefully can make some progress.

Thanks for the quick response.

You should be able to just generate over the existing projects, and reference the new dlls. However there's one caveat: you moved from 5.2 to 5.6, and in 5.4 we moved the csproj files to a different folder. This is documented but you might have missed it (in 'migrating your code'). I think that's the root cause of your problem.


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:
37476 posts
# Posted on: 27-Aug-2019 22:32:05.  
timothyleerussell wrote:
Just as a follow up, I reinstalled 5.6 because I just installed VS 2019 (been waiting for some extensions I need to catch up) and it seemed like an easy way to get the LLBLGen 2019 extension installed.

When I launched the standalone editor for the first time after reinstalling, I got the error again on first launch but not on subsequent launches.

Don't need a reply, just more info for you.

Thanks!
Timothy

Hmm, strange! We still can't reproduce it with those steps... However, we did manage to make sure the original error shows up at least, so it's not causing a crash while being displayed. So in the next build this should at least be less vague and be the right error. Still not helpful (there shouldn't be exceptions at startup) but at least it then can lead to more info what really causes the initial exception so we can fix that Regular Smiley

Btw, in the installation folder of llblgen pro, there are 2 vsix files. You can run these at any time to install the designer in vs, no need to uninstall/reinstall the whole designer Regular Smiley
Frans Bouma
LLBLGen Pro / ORM Profiler Lead Developer | Blog | Twitter
 
Top
timothyleerussell
User



Location:

Joined on:
02-Oct-2008 07:48:55
Posted:
25 posts
# Posted on: 28-Aug-2019 01:54:15.  
Cool, thanks!

  Top
ewe
User



Location:

Joined on:
06-Sep-2013 21:06:15
Posted:
3 posts
# Posted on: 28-Aug-2019 14:59:02.  
Otis wrote:
ewe wrote:
I deleted the two existing projects, and regenerated them from scratch rather than updating. I copied over my extensions to Entity and TypedView classes into new extension folders, and then rebuilt. All of the errors went away. I will try this with my various other LLB gen projects and hopefully can make some progress.

Thanks for the quick response.

You should be able to just generate over the existing projects, and reference the new dlls. However there's one caveat: you moved from 5.2 to 5.6, and in 5.4 we moved the csproj files to a different folder. This is documented but you might have missed it (in 'migrating your code'). I think that's the root cause of your problem.


That was exactly what the problem was. I looked at the VS output, and it was not finding csproj files.

All is well now.
  Top
Pages: 1  


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

Version: 2.1.12172008 Final.