StrataFrame Forum / Updates and Information / Developer Blog Topics

StrataFrame License Diagnostics Tool

Trent L. Taylor — Fri, 12 Feb 2010 13:26:31 GMT

There are times when a license file may be installed but may not act as expected on a developers machine. This is environmental 99.99% of the time. Regardless, it helps to have this simple diagnostic tool so that a StrataFrame technician can better understand what may be going on client-side. Many times, this tool will give you, the developer, the answer with no further explanation from us.

One word of caution, DO NOT POST SCREEN SHOTS of this tool as it contains your serial number and could be used maliciously. Only send these screen shots via email or private message to the StrataFrame Team.

Windows 7, Visual Studio 2008, and Embedded Resources producing compile time errors.

Trent L. Taylor — Wed, 28 Oct 2009 10:38:08 GMT

Like many of you, we are beginning to migrate some of the development machines in house over to Windows 7. Like any migration, there are always things that come up and cause frustration. The first one for me...a generic GDI+ error when compiling. This one took me by surprise (the resolution anyway) as it had to do with pre-existing embedded resources. Here is the error:

[quote]Error 19 The "GenerateResource" task failed unexpectedly.
System.Runtime.InteropServices.ExternalException: A generic error occurred in GDI+.
at System.Drawing.Image.Save(Stream stream, ImageCodecInfo encoder, EncoderParameters encoderParams)
at System.Drawing.Image.Save(MemoryStream stream)
at System.Drawing.Image.System.Runtime.Serialization.ISerializable.GetObjectData(SerializationInfo si, StreamingContext context)
at System.Runtime.Serialization.Formatters.Binary.WriteObjectInfo.InitSerialize(Object obj, ISurrogateSelector surrogateSelector, StreamingContext context, SerObjectInfoInit serObjectInfoInit, IFormatterConverter converter, ObjectWriter objectWriter)
at System.Runtime.Serialization.Formatters.Binary.WriteObjectInfo.Serialize(Object obj, ISurrogateSelector surrogateSelector, StreamingContext context, SerObjectInfoInit serObjectInfoInit, IFormatterConverter converter, ObjectWriter objectWriter)
at System.Runtime.Serialization.Formatters.Binary.ObjectWriter.Serialize(Object graph, Header[] inHeaders, __BinaryWriter serWriter, Boolean fCheck)
at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Serialize(Stream serializationStream, Object graph, Header[] headers, Boolean fCheck)
at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Serialize(Stream serializationStream, Object graph)
at System.Resources.ResourceWriter.WriteValue(ResourceTypeCode typeCode, Object value, BinaryWriter writer, IFormatter objFormatter)
at System.Resources.ResourceWriter.Generate()
at System.Resources.ResourceWriter.Dispose(Boolean disposing)
at System.Resources.ResourceWriter.Close()
at Microsoft.Build.Tasks.ProcessResourceFiles.WriteResources(IResourceWriter writer)
at Microsoft.Build.Tasks.ProcessResourceFiles.WriteResources(String filename)
at Microsoft.Build.Tasks.ProcessResourceFiles.ProcessFile(String inFile, String outFile)
at Microsoft.Build.Tasks.ProcessResourceFiles.Run(TaskLoggingHelper log, ITaskItem[] assemblyFilesList, ArrayList inputs, ArrayList outputs, Boolean sourcePath, String language, String namespacename, String resourcesNamespace, String filename, String classname, Boolean publicClass)
at Microsoft.Build.Tasks.GenerateResource.Execute()[/quote]

Resolution:

This was a bit frustrating, but in this example, it was because the offending image in the resource was a JPG instead of a PNG. 9 times out of 10 we use a PNG image anyway, but in this example, converting the offending image into a PNG then rebuilding the solution resolved the issue.

There is another issue that can come from this as well (per my research). If you have an image that is larger than 64K, this can possible creep up as well.

Hope this helps! :)

Follow us on Twitter

Trent L. Taylor — Thu, 27 Aug 2009 08:48:59 GMT

Follow us on Twitter to learn about new updates and up and coming features. There have been a number of requests for this so we will see how well it works. If well received we will plan to increase the posts to also include new features in production and some fun tidbits about what we are working on and what is coming down the pike.

To follow StrataFrame on Twitter, click here or go to http://twitter.com/strataframe.

Forum Back Up

Trent L. Taylor — Mon, 23 Mar 2009 08:35:02 GMT

The forum has apparently been down (in the sense that no new posts could be added) over the weekend. There was an issue with IIS that has been resolved. Sorry for any trouble that this may have caused.

Sending Anonymous Private Messages

Trent L. Taylor — Mon, 12 Jan 2009 09:27:36 GMT

It is not at all uncommon for me to get a handful of private messages from Anonymous. When this happens, you will never get a response from me as I have absolutely no idea who sent it. Be sure to login to the forum when sending a PM so that it doesn't show up as Anonymous in my inbox.

Also, there is no reason to send direct private messages to StrataFrame developers asking questions that could be asked on the forum. The PMs are generally going to deal with asking questions that do not need to be public information. But asking a standard question to a specific SF developer will only slow down a response. There are many wonderful developers out here so be sure to take advantage of their experience and knowledge by posting your questions where they can be seen.

Thanks! :)

Where's the KB?

Trent L. Taylor — Wed, 23 Jul 2008 09:55:02 GMT

We just wanted to post an update on the status of the KB and when it will be released. We had hoped to already have the KB rolled out at this point, but as many of you can appreciate, things got really busy! We prioritized new SF features and enhancements, many customer requests, ahead of getting the KB out which seemed to be the more prudent things to do.

We will still release a KB and will at some point put a full-court-press on getting the material created and posted. Thanks for your patience and understanding on the delay.

Forum Attachments

Trent L. Taylor — Wed, 23 Jul 2008 09:51:37 GMT

There was an issue with downloading attachments in certain conditions and environments from the web. Some people and machines would run into while others would not. This issue should now be resolved and all attachments should be downloadable from any supported browser.

Design-time issues with Intellisense and APPCRASH using Visual Studio 2008 and VB.NET

Trent L. Taylor — Mon, 18 Feb 2008 15:09:58 GMT

We have run into some issues with Visual Studio, VB.NET, and large projects recently and I thought I would just share this information with you so that you can take some action on your side. The issue that we ran into is that the larger our VB.NET projects became, the slower the response in the .NET editor as well as Intellisense became. Not only that, Visual Studio would just flat out crash...and many times not save your work. This became VERY frustrating...and I am sure that we were not alone :D

Due to our high frustration level, we finally contacted Microsoft and worked through the issue. We were right...we weren't the only people with this issue as they were already in the phase of testing a hotfix. Their initial resolution was to just disable the XML documentation...which just flat out wasn't going to cut it. Though when you did this, the IDE was MUCH faster and the crashes subsided. Today we got a hotfix from Microsoft and so far so good. The Intellisense is much faster, we have our XML docs back, and hopefully this will keep the IDE from dying!

Here was the KB article that was referenced prior to this fix: http://support.microsoft.com/?id=946452 . Even though this article doesn't yet mention a hotfix, one does exist. Just place a call to MS support, tell them your issue, and you should be able to get this fix.

Release 1.6.0

Steve L. Taylor — Thu, 15 Feb 2007 09:05:17 GMT

Good morning all:

Well we are feeling the pressure, sorry for the delay. The truth of the matter is simple yet disconcerting. We were ready to post everything yesterday at 4:30pm CST and it came to our attention that two different blogs are trying to crack the SF licensing. Since the Enterprise Server rises and falls on its licensing I had to stop the guys from publishing the product.

We bought an expensive obfuscator last night and are currently working the process. The minute we are confident we have it we will upload the release. If the process gets to tedious we will split off the Enterprise Server and release SF. That would be worse case. It is my hope we can work through it in the next couple of days.. Days!!!! what about freaking hours -- I feel your thoughts.. :w00t:

I appreciate your patronage and patience,

Steve

All runtime components are pre-localized

Trent L. Taylor — Tue, 19 Dec 2006 12:13:33 GMT

In January we will be releasing the 1.5.2 version of StrataFrame with some wonderful new features. One of these new features is the pre-localized runtime components. All runtime components will already be localized out-of-the-box in the following languages:

English
Spanish
Portuguese
German
French
Italian
Russian

This includes controls such as the MaintenanceFormToolstrip and BrowseDialog as well as applications such as Role Based Security.

Long term, the StrataFrame development environment will also be localized in the same languages so that developers can develop in their native language as well.

But as of the next update (1.5.2), all applications developed using StrataFrame will require no effort whatsoever on the part of the developer in regards to localizing the runtime components! :)

Data Deployment Error when upgrading to Version 1.5

Trent L. Taylor — Sat, 23 Sep 2006 20:15:31 GMT

The StrataFrameSample database has had many changes made to it between versions. Including case sensitive changes, which the DDT now supports and recognizes as a field rename. However, there is a minor issue that has already been verified and we will fix the issue and repost an update once resolved. The issue only pertains to changing an existing fields name by changing the case sensitivity of the lettering without changing the actual name. The error would look something list this:

Workaround
To work around this issue now, simply remove the StrataFrameSample database from your SQL Server install and re-run the StrataFrame installation (it is just fine to do a "Repair"). This database does not contain any pertinent StrataFrame data and is used only for sample purposes. DO NOT REMOVE the StrataFrame database! The StrataFrame database contains all of your BO Mappings, DDT Meta-Data, Security, and Loclization and Messaging data. Remove only the StrataFrameSample database.

Developing on Multiple Computers with a Single License

Trent L. Taylor — Mon, 21 Nov 2005 14:10:18 GMT

There have been several queries about multiple license for those of us who program at night on our laptops and during the day on another computer at the office. How many licenses must I purchase in order to make this happen? Only one. The activation and deactivation process of the Framework takes literally seconds and can be executed as many times as desired. You can also use a USB network adapter as a dongle.

USB Network Adapter Dongle:
Since all activations are tied to a MAC address, you can buy an inexpensive USB network adapter. The network adapter does not have be plugged into the network, just plugged into the USB port and "Enabled". When activating do the following:

1.) Open the Visual Studio IDE on the computer
2.) Click StrataFrame -> License Information from within the Visual Studio IDE.
3.) If already activated, deactive by clicking the "Start" button. Then go back into the License Information window.
4.) Make sure the USB network adapter is plugged into the computer and choose it from the drop-down combo next to the "Network Adaper" label.
5.) Click the "Start" button to activate.
6.) Take the USB network adapter to the next computer and go through this same procedure.

An infinite number of activations are allowed for an active network adapters MAC address. The only requirement is that the USB network adapter be plugged into the USB port while working on any one computer that has activated on that adapter. To move from computer to computer, simply take the USB network adapter and plug it in the USB port of the comptuer on which you are working. This functionality exists for several reasons. First, as a dongle which allows you to activate as many times as you like while only consuming one purchased license. Second, this also allows you to format your computer and re-activate on the same MAC address without first deactivating. This can be a common occurance on development machines when we have to re-format and start over :) as I am sure we have all had to do one time or another.

Deactivate / Reactivate:
Let's assume that I purchase a single StrataFrame Application Framework license and activate it on my work computer. But I installed StrataFrame on both my laptop and my work computer. At the end of the day, I am about to go home and I know that I want to program on my laptop tonight. Do the following:

1.) Open the Visual Studio IDE on the work computer
2.) Click on StrataFrame -> License Information from within the Visual Studio IDE
3.) Deactivate the license on the work computer

(drive home if you want to) ;)

4.) Open the Visual Studio IDE on the laptop
5.) Click on StrataFrame -> License Information from within the Visual Studio IDE
6.) Activate the license on the laptop

This entire process takes literally seconds (minus the driving home portion) and allows the developer to move from computer to computer at will. Simply reverse the process when going back to the work computer.

FYI
The deactivation process does not affect any of your projects and only prevents the type editors and builders from being accessed. Once re-activated all access will be regained.

Application Framework Updates

Ben Chase — Mon, 21 Nov 2005 11:29:05 GMT

[b]Update Process[/b]:

As we diagnose and resolve issues within the Application Framework, we will post updates in 2 manners:

[b]1) Here on the update blog.[/b]
a) We will post a zip file containing the modified DLLs and acompanying files.
b) When you received the modified DLL, you will need to put it into the Global Assembly Cache and the C:\Program Files\Common Files\MicroFour\StrataFrame\ folder. To place the new DLL within the GAC, open the C:\windows\assembly\ folder on your computer and "drag" the DLL into the folder.
c) You will need to restart all instances of Visual Studio for the changes to take effect.
[b]2) Through the Downloads within the My Account area of the StrataFrame website.[/b]
a) This method may be delayed from the updates within the blog as the install will need to be rebuilt before the update will be placed within the downloads.
b) When updating your StrataFrame through this method, you will need to uninstall the previous version of StrataFrame before installing the update. This will ensure that the new assemblies are properly added to the GAC and the other necessary locations.
c) When we update the download available through the My Account area of the StrataFrame website, we will post a notification within this topic.

-----------
It's not whether you find issues, because we know they exist, it's how quickly we can resolve those issues.