Compliments of Shashi…a coworker of mine…

1. Make sure to build your solution in debug mode.
2. Deploy the debug version wsp (located in wsp/debug folder) to Sharepoint
3. copy the .pdb file from bin/debug folder of whatever the solution you would like to debug to clipboard
4. open up the gac folders using – Start-> run -> %systemroot%\assembly\gac_msil
5. Open the folder of the solution you wish to debug till you find the .dll file
6. Copy the copied .pdb file
7. Bring up the site
8. In Visual studio, click on Debug -> Attach Process (make sure “Show processes in all sessions is checked”)
9. attach 2 w3wp.exe process and click on Attach if prompted
10. Set the breakpoints

Go back to site and try to do your activities, if your breakpoint gets hit, it will show you the VS screen and you are good to go….

I think the fact that the DOS prompt is not resizable is a limitation. For a 19″ Dell LCD, the best settings that i’ve found are:

Screen Buffer Size:
Width: 155
Height: 9999

Window Size:
Width: 155
Height: 66

Seems to work well.

I just ran into a situation where I had a Ruby on Rails plugin (Substruct) that I am using for a site release a new version. One big disadvantage of plugins vs. gems in the rails world is versioning because you can modify plugin code. Anyhow, I needed to know what changes were made across the entire plugin directory structure, so that i could easily merge the changes I’ve made to the code changes that were released with the update.

Enter Kdiff, an Free, Open Source, Platform agnostic tool for comparing files and directories.

http://kdiff3.sourceforge.net/

C:\eclipse\eclipse.exe -clean -vargs -vmargs -Xms256m -Xmx512m -XX:MaxPermSize=128m

Every once in a while i come across a pretty sweet flash/flex application…and what makes TitleViewer really cool is that it’s free and configurable.

Overview:

http://www.airtightinteractive.com/projects/tiltviewer/ 

Demo:

http://www.airtightinteractive.com/projects/tiltviewer/app/

Recently i had to search within a couple of hundred JAR files to locate which Java package needed to be included in my build path. Fortunately this isn’t too difficult with the help of Cygwin and a little command line script.

export search="search string"; for file in 'find . -name "*.jar"'; do echo $file; jar -tvf $file|grep $search; done

I recently migrated one of my rails apps from 1.2.6 to 2.0.2. I found that several things have changed or are no longer supported.

For example:

<%start_form_tag%>
...
<%end_form_tag%>

<%form_tag do %>
...
<%end%>

Pagination:

I got the error: undefined method `paginate’ … this is because pagination was ripped out.

The fix is to install the following plugin:

ruby script/plugin install svn://errtheblog.com/svn/plugins/classic_pagination 

Auto_Complete:

I got the error: Undefined method `auto_complete_field’ for #
The fix is to install the following plugin:

ruby script/plugin install http://svn.rubyonrails.org/rails/plugins/auto_complete 

Ok, you’ve probably seen my other posts on how to get JBOSS up and debugging with Eclipse, if note here are the links:

http://jharbs.com/blog/?p=110 and http://jharbs.com/blog/?p=107

To get Apache working with JBOSS you will need to do the following:

You first need to download the Apache webserver version 2.2. You will want to start by installing this version of Apache, currently 2.2.8.

Install this to c:\apache2.2\, you may have to use the advanced / custom install option during your installation.

Once installed, you will need to download these apache and jboss helper files.

The contents includes:

• mod_jk.so which you will need to place in C:\apache2.2\modules
• modk.conf, httpd.conf, and workers.properties which will all need to be placed in C:\apache2.2\conf

cheers.

Check out the ie7-js javascript library. It helps with a bunch of css, layout, hover, PNG support, etc.

 Project Site - http://code.google.com/p/ie7-js/

Demos -  http://ie7-js.googlecode.com/svn/test/index.html

I assume that you’ve seen my last post about how to get JBoss Server setup in Eclipse. Now here is a quick tutorial to get JBoss debugging up and running.

Click on Window>Show View>Other…

Select Server>Servers

In the Servers Tab of Eclipse right click

New>Server

For the options use:

Server’s host name: localhost

Select the server type: JBoss v4.0 ***Not JBoss, a division of Red Hat

JRE: jdk1.5.0_12

Application Server Directory: c:/jboss

On the next screen accept the defaults…

If you plan on using Service Capture to capture net traffic on your local machine, then you should install the server on your LAN IP address, not 127.0.0.1.

Now you just need to make sure that you have your EAR deployed to your JBoss deploy directory.

Click Finish

Now for the grand finally right click on the Server and click on Debug. Done.