Recent Entries

ZeroSSL with IIS 10
Account Breach Monitoring
DBML Visualizer VERY Slow - solved!
Poor Man's SQL Log Shipping (Kinda)
Excel Column Letter To
Easy & Powerful Ecommerce Solution
asp:Menu Flicker on Page_Load - Solved
Windows Server 2008 Install DLL into GAC


Skip Navigation Links.
You are here: Rants, Rave, & Tips


By Ted Krapf on 7/13/2015 7:48 AM

Have an asp:menu that is flickering on (showing all the sub menus) on page_load and/or post back?  Of course you do, because that server control is pretty squirrely.   Here's the simple CSS fix that corrects the issue:

<style type="text/css">
/* fixes ugly menu flicker */
.menu ul li ul { display: none; }
.menu ul li { position: relative;  float: left; list-style: none; }
.menu ul li ul li { width: 100%; }

I've seen numerous "fixes" for Css menu getting flickering while page post back, but the ones I found never included the 3rd line.  If you have sub menus, the 3rd line (.menu ul li ul li) corrects the width and positioning issue.

Cheers and happy coding!

By Ted Krapf on 3/9/2015 3:46 PM
So the need for a client's offline ClickOnce app to have command line parameters came up again. (oh boy).

The Microsoft docs initially spec'd out that you can't do this when the ClickOnce app is an "offline" app.  But since .NET 3.1, there is a trick you can use to make offline ClickOnce command line parameters function.

The scenario is this:

Client has a ClickOnce app that gets updated (redeployed) by their developer frequently The app is Offline, meaning during publishing from Visual Studio, "How will users install the application?" is set to "From a CD-ROM or DVD-ROM", and then "The application will not check for updates". They have Task Scheduler running on their production box and they basically want the app to run at two different times daily, but to have a command line switch to run different features of the app at the different times. The solution, initially, I thought was to simply have the developer put some time based conditions actually in the application...
By Ted Krapf on 3/15/2013 6:47 AM
A client yesterday had a common problem, "Ted I have 100+ Excel documents that I need to be able to quickly search through, and I'd like to combine all those work books into a single .xlsx file so that I can just search in one document."

Sounds simple enough right?  The first thing we tried together was scouring the web for a VBA script to do this.  Seems simple, get a list of the files in a directory, open each doc, and copy and paste its contents into the main document.  Well after an hour of stumbling through VBA syntax, help files, blogs, etc, we just couldn't find one that would work.  The best we found that worked would combine the all the worksheets of all the other documents into the main workbook as worksheets -- still leaving us having to manually copy and paste 100's of worksheets into one.

We had also found an array of different commercial 'combine' tools that ranged from dollars to $1,000's.  Needless to say, being a programmer, I wanted to see how I could do this myself and so I could share the solution with you!...