Check if computer supports 64 bit OS

The easiest way to check if you have a 64 bit processor is to download CPU-Z from http://www.cpuid.com.

CPU-Z is made available as a zip file, unzip it and then run the exe it contains. The program will collect information about your processor and then under the CPU tab, in the instructions column, see if you have any of these AMD64, x86-x64 or EM64T. if you have any of these then your processor is 64 bit.

If your PC has a 64 bit processor then you will be able to run the 32 or 64 bit version of the operating system of your choice. Currently there aren't a huge number of free 64 bit applications for Windows. Details of those that are available can be found here.

SSMS - Can not paste more than 43679 characters from a column in Grid Mode

Ever tried copying large data from Ms SQL Server? Good luck – It only copies 43679 characters. There is no way to increase this limit. A feature request has been filed: https://connect.microsoft.com/SQLServer/feedback/details/499608/ssms-can-not-paste-more-than-43679-characters-from-a-column-in-grid-mode. I don't think this will be fixed anytime soon since the interface is meant to be admin interface and not a developer tool. I found a couple of workarounds with this (esp. for XML data) but my XML is really huge and it takes a lot of processing power to make that work. In short, it does not work for me.

Best option is to right click the cell as shown above and use “Save result as” to export data into say : .cvs file which opens up to reveal the entire cell data. Now copy paste your data into your favorite editor like Notepad++ and use XML Tools to indent it into XML (if it is XML)

Validate WSDL using Eclipse

 

When you create a wsdl file from scratch or use an already designed one, you must make sure it is valid. In other words it should;

• consist of well-formed XML (All tags should be closed and nested properly)

• conform to XML Schema

• comply with the rules and standards defined in WSDL specification

• valid with the rules defined by WS-I (Web services interoperability organization)

Eclipse Web tools project (WTP) provides a very useful tool which validates a wsdl against above rules/standards.
Lets see how we can validate an existing wsdl using Eclipse wtp.
1. Download and install Eclipse wtp
2. Open eclipse IDE
3. Start to create a new wsdl (File --> New --> other --> Web Services --> WSDL)
4. Give a name to the wsdl (you can provide the name of wsdl which needs to be validated) and click on next. Accept the default options and click on Finish.
5. You will see a design view of a new wsdl file. Move to source view by selecting "Source" tab.
6. You will see an skeleton source of the new wsdl. Just remove it. (remove all elements in the wsdl)
7. Copy the contents of your existing wsdl (Suppose it is Myservice.wsdl) and paste in the source tab.
8. Save it by selecting save button in eclipse tool bar.
9. Right click on the wsdl file and select Validate
If your wsdl has errors, those will be shown in problems pane.
You may notice that we create a new wsdl, remove its content and copy the existing (already created) wsdl in to source view of wsdl validator. I suggest that as a work around because I could not find a way to import an existing wsdl directly into wsdl validator.

Building .NET projects using Hudson Continuous Integration

This is a quick start up to getting your .NET Visual Studio projects to build using Hudson Continuous Integration server.

1. Download and install latest version of Java http://java.com/en/
2. Download Hudson server http://hudson-ci.org/. You might get hudson.zip. Rename it as hudson.war. Suppose c:\Hudson\hudson.war
3. Start Hudson using the command java -jar hudson.war You will see the output like -
4. Use the browser and hit http://localhost:8080/ This is the beauty of Hudson. Once you see the Hudson Dashboard it means you are up and running
5. Go to Manage Hudson and if you see a new version of Hudson is available install it
6. Go to Manage Hudson-> Configure System and install the MSBuild plugin, MSTest plugin, NUnit plugin, Violations plugin and NAnt plugin
7. Shut down hudson and start it again. This will get the new version up and running
8. Go to Manage Hudson->System Configuration http://localhost:8080/configure and configure path of MSBuild.exe to point to c:\Windows\Microsoft.NET\Framework\v3.5\msbuild.exe
9. Configure the email settings and NAnt settings etc

At this point installation and configuration is complete. Now to create jobs

1. On the Dashboard Click New job->Build a free-style software project->OK
2. Enter the SVN url of the project [Hudson has built-in SVN support. If you use other source control systems then you might have to install plugins]
3. To test the configuration, press Save and then Build. The source code will be downloaded from the repository and put into the Workspace
4. Click the ‘Add build step’-> ‘Build a Visual Studio project or solution using MSBuild’ Enter the solution file path if you want to build the entire solution or the project path
5. To test the configuration, press Save and then Build. Now the source code should be updated if there any changes and then built using MSBuild. While the build is running you can check the Console log that is updated as the build continues.

That's it folks. Try it and let me know if that works! Hudson is very configurable so you can be creative with your builds and test cases.

PS: I will add pictures shortly.

Cannot Determine MEP

ERROR - GeronimoLog.error(108) | Cannot Determine the MEP
org.apache.axis2.AxisFault: Cannot Determine the MEP
    at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.getMEP(WSDL11ToAxisServiceBuilder.java:2739)
    at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateOperations(WSDL11ToAxisServiceBuilder.java:1286)
    at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populatePortType(WSDL11ToAxisServiceBuilder.java:592)
    at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateEndpoints(WSDL11ToAxisServiceBuilder.java:469)
    at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateService(WSDL11ToAxisServiceBuilder.java:363)
    at org.apache.ode.axis2.hooks.ODEAxisService.createService(ODEAxisService.java:82)
    at org.apache.ode.axis2.ODEServer.createService(ODEServer.java:327)
    at org.apache.ode.axis2.BindingContextImpl.activateMyRoleEndpoint(BindingContextImpl.java:59)
    at org.apache.ode.bpel.engine.ODEProcess.activate(ODEProcess.java:725)
    at org.apache.ode.bpel.engine.BpelServerImpl.register(BpelServerImpl.java:380)
    at org.apache.ode.axis2.ODEServer.handleEvent(ODEServer.java:626)
    at org.apache.ode.axis2.ODEServer.access$100(ODEServer.java:91)
    at org.apache.ode.axis2.ODEServer$ProcessStoreListenerImpl.onProcessStoreEvent(ODEServer.java:613)
    at org.apache.ode.store.ProcessStoreImpl.fireEvent(ProcessStoreImpl.java:517)
    at org.apache.ode.store.ProcessStoreImpl.fireStateChange(ProcessStoreImpl.java:523)
    at org.apache.ode.store.ProcessStoreImpl.deploy(ProcessStoreImpl.java:301)
    at org.apache.ode.axis2.deploy.DeploymentPoller.check(DeploymentPoller.java:144)
    at org.apache.ode.axis2.deploy.DeploymentPoller.access$300(DeploymentPoller.java:55)
    at org.apache.ode.axis2.deploy.DeploymentPoller$PollingThread.run(DeploymentPoller.java:188)


Usually means there is an error in the WSDL

Notepad++ XML Tools plugin

http://sourceforge.net/projects/npp-plugins/files/XML%20Tools/External%20libs/ext_libs.zip/download


http://rhyous.com/2010/06/03/notepad-and-the-xml-tools-plugin/

Associate default language with specific extensions in Notepad++

If you use Notepad++ often, you may notice that it recognizes the type of file you open and provides nice synatx style for the language of the file. For example, it knows .js is a JavaScript file and .css is a CSS file. Each file type has its own unique style settings. There are a lot of these predefined file types, but what if Notepad++ doens’t support a file type you open often? If you want to make a custom file type use the same style of another type, just use the Style Configurator to define your own extensions.

In Notepad++ navigate to Settings > Style Configurator…

Choose a language on the left side that you want your own extension to match (i.e. if I want .configfiles to style like XML then I’d choose XML). In the User ext. field near the bottom, enter in your custom user extension without the dot in front of it (e.g. bpel for *.bpel files). Now open a new file and it will map that new extension to the style you’ve chosen.