MadCap Software Forums

Since the release of Flare 9 (plus relevant updates), I've seen more problems with various actions throwing dotNet (and other framework) exceptions. I hate to be an armchair quarterback here (especially since I've only ever programmed in Assembly, and that was 20 years ago), but the first rule is to fail gracefully, is it not?

Most of these problems cannot seem to be avoided; however, the workaround appears to be either to restart the computer or to delete the project file and re-import it from source control.

Neither Flare 7, nor Flare 8 had this type of persistent error non-trapping.

My jaw is sore from clenching it so often.

if (error) {
meh;
user.dealswithit = 'yup';
}

I'm saying that for years now, but apparently developers don't care. A good number of the errors are also inherited by the shoddy .NET runtime.

Many of my friends are still actively programming, and I rail on them all the time about the shoddy code that devs turnout as a symptom of the "Rapid Application Development" paradigm. RAD is the cancer of development world, and buggy, half-ass code is the tumor, and is allowed to be released for the sake of maintaining a release schedule; what could be done in 1 MB of tight code is released as 50 MB behemoths, clogged with marginally-used libraries, most of whose code lies inert within the application as wasted space. (To stretch the metaphor to its breaking point, it metastasizes through libraries.)

And I haven't even *started* my tirade on the ever-growing dotNet debacle.

I'm troubled that Flare makes such extensive use of the dotNet framework. It's causing us so many problems.

My jaw is hurting again. I suppose I just have to start shaking my fist more, and clenching my jaw less.

I hear ya...I'm working in QA. A sad place to be at times these days.

Have you talked to support? I haven't had any issues with 9.1 and the Dot net frame work, but I am running it on windows 8