Articles Tagged 'dot net'

If you face performance issues with Spira or KronoDesk when the users use Internet Explorer 9.0, there is a known issue in ASP.NET 4.5 that can cause the client to disconnect and all subsequent AJAX calls do not get processed. This article describes the symptoms and the solution.

This article is now obsolete.
Internet Explorer 9 is no longer supported by Spira or KronoDesk.

Sometimes when running the SpiraTeam v4.1 installer to upgrade from an older version of SpiraTeam (same also applies to SpiraTest and SpiraPlan) you will get the error message:
You must install the Microsoft .NET Framework 4.0.30319 even though .NET 4.0, 4.5 or 4.5.1 is installed.

This article is now obsolete.
Current framework requirements listed here.

Sometimes you need to call code libraries from your Rapise tests, for example when the built-in JavaScript scripting engine does not provide the necessary functionality. This guide explains how to call an external DLL from your Rapise test script.

As you move your web applications (such as SpiraTest, SpiraTeam, SpiraPlan, or KronoDesk) to newer encryption protocols such as Transport Layer Security (TLS) 1.2, you will need to make sure the client applications are configured to use the latest version of TLS. Specifically applications using Microsoft .NET may not use the latest version by default.

Sometimes when using RemoteLaunch with a specific plugin (e.g. Selenium), you may get an error such as:

Could not load file or assembly 'WebDriver, Version=2.44.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.

The way to debug this kind of error message is to enable Microsoft .NET Fusion Logging to get more information as to which dependency could not be loaded. This article explains how to turn this on.

This article explains the process for running Selenium WebDriver test scripts written in C# using NUnit, RemoteLaunch and SpiraTest.

This article describes how to resolve the following error message that can occur on new installations of SpiraTest, SpiraPlan, SpiraTeam or KronoDesk when ASP.NET is not correctly configured. This message typically only occurs on Windows Vista, Windows7 or Windows 2008 Server.

HTTP Error 500.21 - Internal Server Error
Handler "PageHandlerFactory-Integrated" has a bad module "ManagedPipelineHandler" in its module list.

When installing SpiraTest/Plan/Team or KronoDesk on a Windows 2008+ server, some of the controls or content in the application does not display correctly.