Tag Archive: Development

Going Beyond Deploy and Pray

We interrupt the Nerd Girl Run retelling for this exciting announcement!

I am pleased to announce I am presenting another webcast for Consultant in Your Pocket. This Wednesday at 10 AM CENTRAL. Also, there will be a giveaway! Check out Chris Miller’s blog for details.

Register here.

Thanks to Lotus and Domino’s rapid application development platform, many developers find themselves in a deploy-and-pray application release cycle. That can be fine for simple applications in uncomplicated environments, but what happens when the feature requests get more and more complex? Come hear about different techniques for managing Lotus and Domino application deployment and how to get beyond deploy-and-pray!

Release Management Tools

As a follow up to my post, “What is your application development cycle?”, I’d like to ask what tools you use for version and release management.

There are a million questions, and a million ways to handle release management. I’m mostly curious about development for Lotus and Domino, and if you roll your own or use third party tools.

MTA: Full disclosure, this topic has interested me enough to present a webcast on some options…check out Consultant In Your Pocket for the information.

A Fix to My Crazy Domino Problem

Behold the power of community.

Yesterday, I blogged about a crazy Domino Designer problem I was having. Many of you commented with suggestions or ideas. One of those suggestions including shutting off the Eclipse LotusScript editor. Guess what? That worked! That isn’t the fix, however, or the end of the story.

Last night on Twitter, I happened to see a tweet from Mary Beth Raven from someone having a problem with LotusScript. The problem was suspiciously like mine. Mary Beth had suggested the user ask Maureen Leland. I pinged Maureen and told her that my problem sounded eerily the same. She took a look and discovered the item “$AssistAction_error” had been added to my wonky agent. Using Noteman, I was easily able to remove the item and all was well with my agent!

This still begs the question of HOW or WHY the item was appended, when there was no error. HOWEVER, I at least have a fix and understand why the code wasn’t displaying correctly.

Please Help Me With A Crazy Domino Problem

I am using Domino Designer, Release 8.5.1 Revision 20090929.1223 (Release 8.5.1) installed in Windows 7 on my laptop. Over the weekend, I updated a LotusScript agent in an application template, located on the server.

On Tuesday, I went into the office and using the same version of Designer, on my Windows XP desktop. Accessing the same application template on the same server, I open the same agent…and the code is old. Basically, while working over the weekend, I had made several changes and saved frequently. The code being shown on my LAPTOP is correct and the latest version. The code shown on my DESKTOP is from an earlier save, and has errors.

To add oddity to this problem, when the code is run, it is the correct and final code. No matter which machine it is run on. When the code is viewed in the debugger it is the correct and final code. When the code is exported to DXL it is the correct and final code. ONLY when viewed in Designer (which is, you know, kind of fricking important) is the code the old code.

Here is what I have tried to figure out the problem:

Different versions of application? Nope, checked several times to be sure the server is the same, the application is the same, everything is the same.
Different users? Nope, tried accessing with different users on different machines, and the same user on different machines. The code is only correct on my laptop.
Local replica? Nope, checked sever times to be sure it’s the server version. In fact, no local replica existed until I tried that as a means for fixing this.
Make a local replica, check it, and replicate to the server? Tried it, didn’t work. Looks good on the laptop, wrong on other workstations.
Export the agent to DXL, compare and import? Exported, they were identical. Imported ANYWAY, still shows incorrectly on workstation.
Different version of Designer? Nope. I am in the 8.5.2 beta, and it didn’t work there either.
The different OS? Nope, installed on another Windows 7 machine, still no love.
Reinstall? Nope. Uninstalled, completely cleaned the machine, reinstalled. No good.

Now, something that may or may not be related. On the workstation, I frequently get the following error:


I did a quick search on google and found that some people had that error and found their LotusScript agents weren’t always compiling. That sounded PERFECT! Except, their resolution didn’t work for me. Their suggestion involved getting rid of antivirus software. Which I tried, and still no love. In fact, I uninstalled the antivirus software, uninstalled Notes, reinstalled Notes and tried again.

Anyway, seeing that the error involved Java, I made some comparisons there. Hmmm, laptop on Java 6, update 16. So put other machines on same version. Still not working.

So, anyone? Any thoughts? Suggestions? At this point, I am ready to sacrifice chickens or something, if it will work.

Modified to add all the things I tried and already forgot that I tried:

Removed the app from desktop and bookmarks
Deleted cache.ndk
Deleted the workspace
Fixup Updall Compact on the app
New Copy of the template
Copied just the agent into a new blank application

Nada zip nothing. Still broken. Fun, right?

Round and Round

So the other day I discussed @Transform. While @Round may not transform your life, it is important to know about.

Us application developer types may not be numbers people. And Lotus Notes isn’t exactly known for its number functionality. You probably aren’t calculating complex mathematical equations in your Notes applications. However, even if you are calculating simple calculations, you need to know about @Round.

Note that:

3.3 * 3.3 = 10.89


3.33333 * 3.33333 = 11.11

No big deal, right? Except if these calculations are on a much larger scale. And if they are compounded by further calculations on the results.

Enter @Round

Determine where the decimal place should go, and apply it consistently with @Round.

@Round (value, factor)

@Round (10.555, 0.1) = 10.6

Note that the syntax for the LotusScript method Round is slightly different. The second parameter is simply the number of digits after the decimal place, not a factor. In LotusScript, Round (10.555, 1) = 10.6.

Older posts «

» Newer posts