tea time with meowkins

Fix Copy-Paste, Scrolling & Resize in Popup From SharePoint

This is very easy to do, you just have to know what to look for.

First, if generating the popup using the showModalDialog javascript method, try changing this to window.open instead to enable copy-paste.

Next, to fix the scrolling and resizing, added the scrollbar=yes and resizable=yes features to the feature parameter of the window.open method.

Here's what the code will look like:

window.open('/_layouts/ConfigureReport.aspx?SITEURL={SiteUrl}&ITEMURL={ItemUrl}&ITEMID={ItemId}&LISTID={ListId}&ACTION={ASSEMBLE}','','height=900,width=850,scrollbars=yes,resizable=yes');

Sharepoint Web Part Maintenence Page URL

UPDATE: You can just append "?contents=1" to the web part page.  Thank you, Dennis!

I can never remember this, so i'm saving it on my blog.

http://luigi/reporting/_layouts/spcontnt.aspx?url=%2freporting%2fdefault.aspx

“Type is not registered as safe” Error, When SafeControl Entry is Valid

When you add a web part, if you get an error saying "The type is not registered as safe," even though you do have a valid SafeControl entry for your web parts, then try adding the assembly's strong name to each .webpart file.

Here's an example. The assembly is ArrowWebParts.dll. It's strong name is "ArrowWebParts, Version=3.0.0.1, Culture=neutral, PublicKeyToken=bface3e8a4e95820". Originally, in the type element, I just had "ArrowWebParts.DataDefinitionWebPart", and I was getting the error. After adding the strong name, the error goes away!

<webParts>

<webPart xmlns="http://schemas.microsoft.com/WebPart/v3">

<metaData>

<type name="ArrowWebParts.DataDefinitionWebPart, ArrowWebParts, Version=3.0.0.1, Culture=neutral, PublicKeyToken=bface3e8a4e95820" />

<importErrorMessage>Cannot import ArrowWebParts.DataDefinitionWebPart.</importErrorMessage>

</metaData>

<data>

<properties>

<property name="AllowZoneChange" type="bool">True</property>

<property name="ExportMode" type="exportmode">All</property>

<property name="HelpUrl" type="string" />

<property name="Hidden" type="bool">False</property>

<property name="TitleUrl" type="string" />

<property name="Description" type="string">Wizard for creating a Windward data profile.</property>

<property name="AllowHide" type="bool">True</property>

<property name="AllowMinimize" type="bool">True</property>

<property name="Title" type="string">Create Windward Data Profile</property>

<property name="ChromeType" type="chrometype">Default</property>

<property name="AllowConnect" type="bool">True</property>

<property name="Width" type="unit" />

<property name="Height" type="unit" />

<property name="HelpMode" type="helpmode">Navigate</property>

<property name="CatalogIconImageUrl" type="string" />

<property name="AllowEdit" type="bool">True</property>

<property name="TitleIconImageUrl" type="string" />

<property name="Direction" type="direction">NotSet</property>

<property name="AllowClose" type="bool">True</property>

<property name="ChromeState" type="chromestate">Normal</property>

</properties>

</data>

</webPart>

</webParts>

Ant "Unable To Locate tools.jar", Wrong JDK/Java Version

When you run ant, if you get an error/warning that says unable to locate tools.jar, eg:

Unable to locate tools.jar. Expected to find it in C:\Program Files\Java\jre6\lib\tools.jar

or you're seeing the wrong java version from the one you set in JAVA_HOME, then try changing your JAVA_HOME environment variable.  Mine was set to "C:\Program Files\Java\jdk5\bin", and I had to remove the "\bin" part, because ant looks for "%JAVA_HOME%\bin\java*". So for example, with the "\bin" part, ant looks for "C:\Program Files\Java\jdk5\bin\bin\java.exe".

Programming Tips From Tomas

• Get away from the desk every now and then. Helps your mind stay sharp.
• Wrap untyped data into objects to make them typed. Saves time by revealing errors at compile time vs runtime.
• Override toString() or equiv. Makes debugging much faster and easier.
• Remember that knowledge is not reality, but the form of the mind, and therefore, no matter what you "know" you may be mistaken.
• Always write a functional unit test for each feature. Otherwise you'll break your app by accident.
• Break helper methods out of your larger methods frequently. It will help you understand what is going on more quickly.
• Write scripts/batch files to help with your compiling/building/deployment. may take learning, but saves tons of time.
• Validate your inputs. If some input has an invalid value, it will be a lot easier to identify if you throw a specific exception than if you just let one of the sub-commands fail in a mysterious way.
• Use specific exceptions with helpful messages. Saves phone calls and screen shares. Also demands that you understand what is going on with code you are working on or using.