StrataFrame Forum » StrataFrame Application Framework - V1 » Issues » Install Issues Strataframe 1.5.1

Install Issues Strataframe 1.5.1

Ronald J Clarke — Tue, 19 Dec 2006 19:29:25 GMT

I've run into two issues installing 1.5.1. The first issue delt with the existance of Strataframe tutorial database files in the SQL Server directory. The log file correctly identified the problem but I could not end the install application. I had to kill the application through the task manager; however this did not get rid of the install progress window which lists the steps being executed. I had not choice but to re-boot.

The second issue occurred on another machine (running Vista RTM). There are two log files with the same date/time so I am providing both in the attached zip file. The error describes a problem with the output buffer being too small for the unicode encoding.

RE: Install Issues Strataframe 1.5.1

Hugo R. Figueroa — Tue, 19 Dec 2006 19:29:25 GMT

It Is good to know that.

Thank you.

RE: Install Issues Strataframe 1.5.1

Ivan George Borges — Mon, 11 Dec 2006 11:35:21 GMT

[quote](I'm coming from VFP and I am new to .net, but I think that I can go ahead thanks to Strataframe) :)[/quote]

Hi Hugo.

Welcome to the club.;)

I was in the exact position 4 months ago. I'm still getting used to VB.NET, and still working with VFP a lot. But in the first month I had a nice application running in .NET thanks to StrataFrame, I'm sure you will enjoy it too.

Cheers.

RE: Install Issues Strataframe 1.5.1

Hugo R. Figueroa — Sun, 10 Dec 2006 19:02:57 GMT

I've installed Strataframe in a Windows Vista machine and have the same problem described here, so it is good to know it'll be addressed in the next release.

( I am trying Strataframe and I made some testings with Infragistics controls and it seems pretty cool).

(I'm coming from VFP and I am new to .net, but I think that I can go ahead thanks to Strataframe) :)

RE: Install Issues Strataframe 1.5.1

Trent L. Taylor — Sun, 10 Dec 2006 12:16:47 GMT

Vista support has already been addressed and will be available in the 1.5.2 release. The issue has to do with default encoding format differences between the OS.