Build 242

[ScottMDA]

Hi Tim!

This build is working much better for me than 240. Thanks very much.

Scott

[tim arnot]

Glad to hear :)

[nbrich1]

Hmmm, for some reason 242 won't start up. Executable run  (Run regular as well as admin- same result:
splash screen displays then Closes/CTD).  (Faulting Module- KERNELBASE.dll) and .NET Runtime error:

Faulting application name: Plan-G.exe, version: 4.0.0.242, time stamp: 0x60776c81
Faulting module name: KERNELBASE.dll, version: 10.0.19041.964, time stamp: 0x11253621
Exception code: 0xe0434352
Fault offset: 0x0012a6e2
Faulting process id: 0x213c
Faulting application start time: 0x01d753bbd83e2459
Faulting application path: C:\Flightsim Programs\Plan-G_v4 Beta Build 242\Plan-G.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: 1b66d2e6-b3a9-4b8a-b9be-87c11ed648ed
Faulting package full name:
Faulting package-relative application ID:
----------------------------------------------

Application: Plan-G.exe
CoreCLR Version: 4.700.21.21202
.NET Core Version: 3.1.15
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Windows.Markup.XamlParseException: The invocation of the constructor on type 'Plan_G.ViewModel.ViewModelLocator' that matches the specified binding constraints threw an exception.
---> System.TypeInitializationException: The type initializer for 'Plan_G.Data.Logbook' threw an exception.
---> Microsoft.Data.Sqlite.SqliteException (0x80004005): SQLite Error 14: 'unable to open database file'.
   at Microsoft.Data.Sqlite.SqliteException.ThrowExceptionForRC(Int32 rc, sqlite3 db)
   at Microsoft.Data.Sqlite.SqliteConnection.Open()
   at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.OpenDbConnection(Boolean errorsExpected)
   at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.OpenInternal(Boolean errorsExpected)
   at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.Open(Boolean errorsExpected)
   at Microsoft.EntityFrameworkCore.Sqlite.Storage.Internal.SqliteDatabaseCreator.Create()
   at Microsoft.EntityFrameworkCore.Storage.RelationalDatabaseCreator.EnsureCreated()
   at Microsoft.EntityFrameworkCore.Infrastructure.DatabaseFacade.EnsureCreated()
   at Plan_G.Data.EF_LogbookDataContext..ctor() in C:\Users\Tim\source\repos\Plan-G\Data\EF_Logbook.cs:line 209
   at Plan_G.Data.Logbook..cctor() in C:\Users\Tim\source\repos\Plan-G\Data\Logbook.cs:line 35
   --- End of inner exception stack trace ---
   at Plan_G.Data.Logbook.QueryAircraftList() in C:\Users\Tim\source\repos\Plan-G\Data\Logbook.cs:line 1454
   at Plan_G.ViewModel.LogbookAirframeDetailViewModel..ctor() in C:\Users\Tim\source\repos\Plan-G\ViewModel\LogbookAirframeDetailViewModel.cs:line 239
   at Plan_G.ViewModel.ViewModelLocator.CreateLogbookAirframeDetailViewModel() in C:\Users\Tim\source\repos\Plan-G\ViewModel\ViewModelLocator.cs:line 2565
   at Plan_G.ViewModel.ViewModelLocator..ctor() in C:\Users\Tim\source\repos\Plan-G\ViewModel\ViewModelLocator.cs:line 3907
   --- End of inner exception stack trace ---
   at System.Windows.Markup.XamlReader.RewrapException(Exception e, IXamlLineInfo lineInfo, Uri baseUri)
   at System.Windows.Markup.WpfXamlLoader.Load(XamlReader xamlReader, IXamlObjectWriterFactory writerFactory, Boolean skipJournaledProperties, Object rootObject, XamlObjectWriterSettings settings, Uri baseUri)
   at System.Windows.Markup.WpfXamlLoader.LoadBaml(XamlReader xamlReader, Boolean skipJournaledProperties, Object rootObject, XamlAccessLevel accessLevel, Uri baseUri)
   at System.Windows.Markup.XamlReader.LoadBaml(Stream stream, ParserContext parserContext, Object parent, Boolean closeStream)
   at System.Windows.Application.LoadBamlStreamWithSyncInfo(Stream stream, ParserContext pc)
   at System.Windows.Application.LoadComponent(Uri resourceLocator, Boolean bSkipJournaledProperties)
   at System.Windows.Application.DoStartup()
   at System.Windows.Application.<.ctor>b__1_0(Object unused)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
   at System.Windows.Threading.DispatcherOperation.InvokeImpl()
   at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(Object state)
   at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(Object obj)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location where exception was thrown ---
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at MS.Internal.CulturePreservingExecutionContext.Run(CulturePreservingExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Windows.Threading.DispatcherOperation.Invoke()
   at System.Windows.Threading.Dispatcher.ProcessQueue()
   at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
   at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
   at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
   at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)
   at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)
   at System.Windows.Threading.Dispatcher.PushFrame(DispatcherFrame frame)
   at System.Windows.Threading.Dispatcher.Run()
   at System.Windows.Application.RunDispatcher(Object ignore)
   at System.Windows.Application.RunInternal(Window window)
   at System.Windows.Application.Run()
   at Plan_G.App.Main()

(I have Plan-G_3.2.2.167 and Plan-G_v4 Alpha Build 240 are both working perfect.. 
but Plan-G_v4 Beta Build 242 won't fire up.    (dotnet-runtime-3.1.12-win-x86.exe) is installed.

Any ideas Tim? > NET runtime version correct?  (Or maybe I don't have c:\user\Tim on my pc so have no sources?).


Norm

[tim arnot]

Try deleting your Plan-G Files\Data\Plan-G_Logbook.db file and see if it'll start then.

[liamgibbins]

I had the same problem with a fresh download...
Maybe repack the zip without the .db file?
Was scratching my head for ages then lol...

Great work btw.. :)

[nbrich1]

Ok Tim... figured it out..  (Logbook db had nothing to do it cause none of the db files can be found). My existing data folder was not named Plan-Gv4 Files. (I had mine set and cfg as Plan-G v4 Files.  (space between Plan-G and v4 Files. (on purpose).   But 242 is not creating a default Plan-Gv4 Files data folder/files hence will not start.

So the beta v4 build 242 is trying to start, but can't find the data (and since it is not creating a default set) it has no source or parameters hence CTD. (This version (build 242) does not create it's own db Plan-Gv4 Files folder or data files for some reason).   

I renamed my previous "Plan-G v4 Files" data folder back to your default named "Plan-Gv4 Files" and tried it again: Build 242 upon startup now found my old previous 240 db data files and therefore started up.   (but 242 itself does not create a data folder hence to use 242 a previous version a data folder must already be in place and the folder named Plan-Gv4 Files) or CTD.

So for a new user, build 242 as is will not work as upon startup as it does not create the required data folder Plan-Gv4 Files or db files required to startup. Also for anyone who requires/wants a separate or different named db data folder name (for whatever reason), can no longer do this in 242.   

So right now I have build 242 using the build 240 data files (which I don't want to do) and 242 is not creating default data in which to be able to startup.

Hope this now explains the issue. The  data folder "Plan-Gv4 Files" appears to be hard coded somewhere but a default is not being created upon when Plan G exe is run.

Now after getting into 242, do see Options/Locations that can be configured/change.. but that would only work  if data folder/files are already in place prior to 242 Plan G initialization/startup. (242 does not create a default data folder/files that are required.)

(When the exe is run, if Plan Gv4 files Folder is not present a default needs to be created to enable the app to startup).

Hope this helps and explains.

Norm

[tim arnot]

Thanks. Not sure why it isn

[nbrich1]

Test: rename your data folder.....  x:\documents\Plan Gv4 Files  to Plan Gv4 FilesOFF   

Then try to do a fresh 242 from the zip. The run the executable and see if it creates the documents folder "Plan Gv4 Files" and has db default files or goes CTD.  If no data created then it will CTD. Suspect something broken in the zip to create a default set of db folder/files to start. 
If yours does create the default "Plan Gv4 Files" folder and db files upon startup then I have an issue somewhere!!

(Just tried this again with build 240 and confirmed that it works fine in 240 to create the documents\Plan Gv4 Files  folder and files, whereas build 242 doesn't not).

Norm

[tim arnot]

It's attempting to access the logbook before it does the CheckCreate test for the folder. It'll be fixed in the next build.

[nbrich1]

Ah ok, makes sense then. Thanks Tim.

[tim arnot]

New build is up. :)