AvatarScriptLink.NET version 1.2.0 is now available on NuGet.
This release includes the introduction of Builder methods to assist with the creation of the various objects as well as allowing for the error code and error message to be set prior to calling ToReturnOptionObject().
This is especially helpful when arranging unit tests.
AvatarScriptLink.NET version 1.1.10 is now available on NuGet.
AvatarScriptLink.NET version 1.1.6 is now available on NuGet. This release refines the behavior of setting a FieldObject as required or optional.
With the release:
SetRequiredField() will no longer set the FieldObject as Enabled as well. Use SetEnabledField() as well if this is the desired result.SetDisabledField() will no longer set the FieldObject as Optional as well. Use SetOptionalField() well if this is the desired result.AvatarScriptLink.NET version 1.0.28 is now available on NuGet. This release addresses security vulnerabilities identified in Newtonsoft.Json and includes miscellaneous updates to other project dependencies.
AvatarScriptLink.NET version 1.0.25 is now available on NuGet. This is a maintenance release which includes updates to miscellaneous project dependencies.
AvatarScriptLink.NET version 1.0.22 is now available on NuGet.
AvatarScriptLink.NET version 1.0.7 is now available on NuGet.
AvatarScriptLink.NET version 1.0.6 is now available on NuGet.
Placeholder for general availability announcement.
Welcome back to my series on getting started with myAvatar ScriptLink. Today, we are looking at testing. As tempting as it may be, we should not wait to test our ScriptLink APIs until they are available in production. We want to test our code before it impacts the users. In our first test, we will set up SoapUI to send a request to our development environment and verify the response.
When we left off, we had created our first Hello World ScriptLink API in .NET using C# and Visual Basic. If we created them correctly, the we should be able to call the RunScript method with the HelloWorld parameter and receive an Error Code 3 with the ErrorMsg "Hello, World!'. Let’s test that.