This project has moved and is read-only. For the latest updates, please go here.

Updated EXE?

Aug 10, 2012 at 1:15 PM

Hello,

 

Been waiting for either the dev resources to become easily available again, or for an updated build of both the current version and the test version.

 

Also, is there an IRC channel to help facilitate faster communication?

 

Thanks!

Aug 10, 2012 at 10:18 PM
Edited Aug 10, 2012 at 10:19 PM

 

I had to shut down the build agent last night, but all should be operational now...

Latest (pre-release / dev) builds can be downloaded here:

Setup / Installer: http://goo.gl/6XXPj

No Installer, just run: http://goo.gl/EtEKV

 

 

No IRC has been setup.  Honestly I doubt I would be able to get on IRC all the time to actually support it in any reasonable fashion.  With that said, if you want to get a room setup on EfNet or something, throw (your/some) bots in there, feel free and we will advertise it on the home page of the project.

 

Aug 13, 2012 at 1:03 PM
Edited Aug 13, 2012 at 1:05 PM

Rob,

Thanks for all your work.

However, when trying to install on a 2008 R2 server, I get this error:

Product: Terminals -- Error 1001. Error 1001. Exception occurred while initializing the installation:
System.BadImageFormatException: Could not load file or assembly 'file:///C:\Program Files (x86)\Terminals\Terminals.exe' or one of its dependencies. This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded..

This is the .NET config on this server:

<32Bit>
1.1.4322.573
  ->C:\Windows\Microsoft.NET\Framework\v1.1.4322
2.0.50727.5456
  ->C:\Windows\Microsoft.NET\Framework\v2.0.50727
4.0.30319.269
  ->C:\Windows\Microsoft.NET\Framework\v4.0.30319

<64Bit>
2.0.50727.5456
  ->C:\Windows\Microsoft.NET\Framework64\v2.0.50727
4.0.30319.269
  ->C:\Windows\Microsoft.NET\Framework64\v4.0.30319

< Installed .NET Frameworks >
.NET FW 1.1
.NET FW 2.0 SP 2
.NET FW 3.0 SP 2
.NET FW 3.5 SP 1
.NET FW 4.0 Client
.NET FW 4.0 Full

Aug 16, 2012 at 2:19 PM

Some direction here would be great.  I can't be the only one seeing this error.

Aug 17, 2012 at 5:15 PM

 

I'm hoping to have some spare cycles this weekend to get it building correctly.  In the mean time make sure you backup your config file(s) and try to uninstall the app, and re-install the new version.  See if that works...

 

Aug 18, 2012 at 12:26 AM

 

System.BadImageFormatException: Could not load file or assembly 'file:///C:\Program Files (x86)\Terminals\Terminals.exe' or one of its dependencies. This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded..

I would suggest trying the non-installer version.

I haven't checked the source code, but I have seen a error like this on another project which was because the setup project was marked as requiring Framework 2 and so the setup was hosted using Framework 2 and was then unable to read some of  the files inside the msi file which were for framework 4.

If it is this issue, then it is only an installer issue and if you extract the files from the zip file, you should then be able to run the program.

Aug 18, 2012 at 11:16 AM

Custom Installer step project was set to .NET 2.0. I changed this. You can try latest nightly build. If it doesn't help, than you have to wait until we will update the setup. Please understand, that we are still in development phase, so the setup isn't finished and will take place as last step.

Nov 22, 2012 at 5:51 PM
Edited Nov 22, 2012 at 5:52 PM

 

I decided to make the build server public to guest users.

Last Successful builds can be found here:

http://goo.gl/bTlqr

And this build is a main compile, and unit tests:

http://goo.gl/nFdxs

 

Nov 22, 2012 at 5:57 PM

WOOT!!

Unit tests are actually being executed!

Tests failed: 21 (21 new), passed: 8

Looks like a sql connection string issue more than anything..

 

Initialization method Tests.SqlCredentialsTest.TestInitialize threw exception. System.Data.EntityException: System.Data.EntityException: The underlying provider failed on Open. ---> System.Data.SqlClient.SqlException: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible

Nov 22, 2012 at 9:46 PM

Udated in Developer quide: http://terminals.codeplex.com/wikipage?title=Developer%20guide