In flow path , to add tabs you need to be sure you have set a snap to
or it will not add tabs

snap to nearest is easiest.

the tab button is the bottom on the left side closest to the draw panel, it looks like two Ls one up one down

Flow jet cutting from an illustrator file.

There is a special export trick for exporting AI files to work in flow.

It's on page 8 of the flowjet SBU document

here it is in summary

edit_>preferences->units make sure it's inches
File-> save as-> save as .ai file
when you click save, in teh top field select "illustrator 3" as your version #
openthe file in corel draw
gott file-> export, delct DXF - AutoCad
when you select export in the top field select "autocad r10"

the segments will be disconnected bu flowpath can autopath it.

RDLC alternating row color, by group instead of by line

A common task in RDLC reporting is alternate row styling, here are the 3 most common types.



Regular alternating row styles



= iif(RowNumber(Nothing) mod 2,  "LightGrey", "Transparent")





Alternating group colors:

http://bidn.com/blogs/briankmcdonald/bidn-blog/713/alternating-group-colors





Alternating group colors with alternating row colors inside the group.

http://www.bidn.com/blogs/briankmcdonald/bidn-blog/717/alternating-group-colors-and-alternating-row-colors

Structuremap 202 errors..... The two most powerful lines for fixing 202 type errors in Structure map.

 If you are using strcutrue map you are familiar with 202 errors.

If you've seen my list of them and their causes it's a big help in fixing them.

Either way here are two powerful lines for diagnosing what's wrong.


#1:

Debug.WriteLine( ObjectFactory.WhatDoIHave() );






Writes out everything loaded by Structure map... like this:

....
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

ICodeDAL (JCDCHelper.DBCodes.Interfaces.ICodeDAL) JCDCHelper.DBCodes.DataObjects.CodeDAL, JCDCHelper.DBCodes, Version=3.1.2.2, Culture=neutral, PublicKeyToken=null JCDCHelper.DBCodes.DataObjects.CodeDAL, JCDCHelper.DBCodes, Version=3.1.2.2, Culture=neutral, PublicKeyToken=null

Scoped as: PerRequest

-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

ISpamisCodeDAL (JCDCHelper.DBCodes.Interfaces.ISpamisCodeDAL) JCDCHelper.DBCodes.DataObjects.SpamisCodeDAL, JCDCHelper.DBCodes, Version=3.1.2.2, Culture=neutral, PublicKeyToken=null JCDCHelper.DBCodes.DataObjects.SpamisCodeDAL, JCDCHelper.DBCodes, Version=3.1.2.2, Culture=neutral, PublicKeyToken=null

Scoped as: PerRequest
....







and #2:
ObjectFactory.AssertConfigurationIsValid();





Looks for obvious errors and gives you better information to fix them... are you haunted by the words "Or one of it's dependencies" this is the tool for you.

Give them a try... Not magic bullets, but a huge help.

Good luck

Cal-

RDLC Repeating Headers on each page.

When you check the repeat headers on each page in an RDLC report
the headers don't actually repeat.

To fix this follow the steps here:

http://bidn.com/blogs/SMcDonald/bidn-blog/1696/scrolling-column-headers-static-header-columns

JCDC 4 digit Version System (Versioning)

The 4 Digit Build Number Versioning System

Here is how I think  we should do the 4 digit build numbering system



A.B.C.D



A = Major version number, I.e. Each time you do a complete rewrite, increment this number.



B = Breaking Change Number. Each time you release a change that will require your users to change their code, increment this number.
       (For Nuget Packages, we increment this package only for the one that's altered manually, If package A causes a change in package B, but B does not cause a change to package C, only A has a breaking change)



C = Production Build Number = Each time you release to prod, increment this number.
       (For Nuget Packages, we ignore this number)



D = Dev\QA Build Number Each time you build to go to QA increment this number.
       (For Nuget Packages, we only increment this number)




Offical JCDC Description:

Note: Follow these rules to increment the version numbers:

X.x.x.x - We increment the leftmost digit by one when we make major changes to the apps (such as from 2G to 3G)

x.X.x.x - We increment the second-to-the-left digit when we make significant changes to a JCDCHelper project that require code changes to the remaining JCDCHelper projects that depend on this one.

x.x.X.x - We increment the third-to-the-left digit when we make changes to a single JCDCHelper project that don’t require code changes to the other packages (but you still need to update the JCDCHelper projects that depend on this single project)

x.x.x.X - We increment the rightmost digit when we don’t make code changes to a single JCDCHelper project, only need to release that project.

NUGet error
 

I just used your solution copier tool (do eeet!) to get a working start on a jcdchelper project.　 Now I’m trying to redo the nuget packages, but package manager console is giving me

Arithmetic operation resulted in an overflow.


Current Theory - You typed the Path with the wrong case when you had the tool rename the project, OR the tool itself renamed the project. so JCDC Heleper Becase JcdcHelper or something similar causeing the paths to be internally inconsistant in the project.

First attempt: edit the nuget.config file to fix teh capitalization error.

Second Attempt:
1 Delete all teh packages.config files, copy from a working project and modify by hand.

retest.

3rd attempt

if no joy, Manually remove all nuget stuff from all projects (ncludeing refereces) and rebuild it by hand. this worked for Jeffery