Imtech Fields Explorer Visual Studio 2008 plugin

, , , , ,

For the last couple of weeks we’ve been thinking here at Imtech ICT Velocity about how we could improve our SharePoint development process. During the last year we have gathered a lot of different tools which help us to automate the routine. And while they all are definitely very useful, they make the development environment quite complex. Maybe even too complex. One of the improvements we thought about was integrating all these different tools we have made into Visual Studio. Imtech Fields Explorer is the first one to go.

Imtech Fields Explorer: how it all started?

Imtech Fields Explorer is one of the tools we really use a lot. It all started with the inability of exploring properties of Site Columns and Content Types and the Internal Names in particular. We needed a simple tool which would allow us to quickly find the field names we need to enter in CAML queries and controls.

When the first version came out we thought that it would be extremely useful and time saving to be able to export the Site Columns and Content Types to XML. Initially I wrote some code to do that but eventually I asked Andrew Connell whether I could include his WCM STSADM commands’ code in Imtech Fields Explorer.

Just recently an idea of yet another improvement was born: why not generate C# wrapper classes to simplify working with Site Columns and Content Types in code? Imtech Fields Explorer was the tool to make it done. Another benefit we got was intellisense: just as you have it for SharePoint built in fields.

Right after that I came up with another idea: how about we let Imtech Fields Explorer generate whole Page Layouts for us? Of course we cannot make it render the complete HTML markup, but even something simple as having all the fields as controls on the page was great. This functionality allowed to cut quite a few hours on the development process.

Imtech Fields Explorer Visual Studio 2008

In the last few months we have discussed it a couple of times how we could create a better experience while developing SharePoint solutions. One of the things we came up with was integrating all our tools inside Visual Studio making it the SharePoint developer’s desktop. Imtech Fields Explorer is only the top of the iceberg but the concept has given us a great start for 2009.

Imtech Fields Explorer for Visual Studio 2008 installer screen

For the last couple of weeks one of my colleagues at Imtech ICT Velocity – Jeffrey Schmitz has worked on moving Imtech Fields Explorer into Visual Studio 2008 IDE. Just last week he finally pulled it off! From now on Imtech Fields Explorer is available as a Visual Studio 2008 plugin.

You can find Imtech Fields Explorer under the View menu: at the same place as other tool panes.

Imtech Fields Explorer is added to the Visual Studio View menu

Because we’re using Visual Studio as the environment, we have decided to remove Fields Explorer’s property grid and display properties in the Visual Studio Properties pane:

Exploring properties of a Content Types using the integrated Properties pane

One of the coolest things of having the Imtech Fields Explorer inside Visual Studio is that when you let it export Site Columns/Content Types to XML or to generate code for you, the file is open inside Visual Studio where you can directly add it to your Solution:

All files generated by Imtech Fields Explorer are being opened inside Visual Studio so that they can easily get added to your solution

No thing is without a downside. We’ve moved Imtech Fields Explorer to Visual Studio but we’re still using the SharePoint Object Model for communicating with SharePoint. If you’re developing remotely this version of the add-on will be of no use to you, unfortunately. Since we all develop locally here at Imtech ICT Velocity it wasn’t the highest priority to replace the SharePoint API with SharePoint Web Services. It doesn’t mean however that we won’t do it in the future. It’s all up to you and the feedback you will provide us.

Imtech Fields Explorer for Visual Studio 2008 ships with an installer so there are no manual steps required in order to get it working. Simply fire up the MSI, click Next a couple of times and Fields Explorer should be available in your Visual Studio 2008.

I’ve been using Imtech Fields Explorer for Visual Studio 2008 for a couple of days myself and I have to admit that Jeffrey has done a lot of great work in the last few weeks. I really love the idea of having all the tools in one place and I’m quite sure that’s the course we will pick for the 2009.

Go on and check out Imtech Fields Explorer for Visual Studio 2008 (441KB, MSI)

Possibly related posts

20 Responses to “Imtech Fields Explorer Visual Studio 2008 plugin”

  1. Xristos K Says:

    Newbiew question: have you considered this article :The Other Internal Column Names & Finding Field Types (http://www.heathersolomon.com/blog/articles/customitemstyle.aspx#ColNameFT)

  2. Waldek Mastykarz Says:

    @Xristos K: Sure, I've seen Heather's article before. Personally I prefer to have more overview of the Site Columns and Content Types rather than exploring the HTML. On the other hands it's okay if it works for you.

  3. James Says:

    I\'m trying to use this within the WSS SP1 VPC download (http://www.microsoft.com/downloads/details.aspx?familyid=1beeac6f-2ea1-4769-9948-74a74bd604fa&displaylang=en) and it is causing VS to crash. Any ideas?

    I\'m not sure if its the same issue but the non VS version also fails to open.

    The event log shows this:

    EventType clr20r3, P1 devenv.exe, P2 9.0.21022.8, P3 47317b3d, P4 fieldsexplorervsaddin, P5 1.0.0.0, P6 494ba498, P7 a4, P8 13, P9 system.typeinitialization, P10 NIL.

  4. Waldek Mastykarz Says:

    @James: Do you know which version of Visual Studio is in the VPC? Do you have any more details on the failure of the non-VS version?

  5. James Says:

    VS 2008 Professional RTM (plus VSEWSS1.2 and several Hotfixes). I can see the Fields Explorer and navigate Content Types etc. but when I export to XML it crashes.

    The non-VS version doesn't cause any errors in the event log. I see the process start up in Task Manager but it disappears again straight away. Any ideas how I could get more info for you?

  6. Waldek Mastykarz Says:

    To provide the export to XML functionality I have used the AC's WCM Custom Commands for STSADM.EXE code (available @ http://andrewconnell.com/blog/articles/MossStsadmWcmCommands.aspx). Could you check whether the original code works on your environment?

  7. James Says:

    I will have to check this tomorrow now. I'll get back to you.

  8. James Says:

    I've installed the STSADM extensions and the ContentType export worked.

  9. Waldek Mastykarz Says:

    @James: thanks for checking. The only thing I could do is to compare my code with AC's. Unfortunately cannot give any promise on when I'll be able to do that.

  10. James Says:

    No worries. I'm only playing around on that server, I will try the software on a self-built server in the next few days so I'll let you know if the problem persists.

  11. Waldek Mastykarz Says:

    @James: great, looking forward to your feedback

  12. Sherman Woo Says:

    Hi Waldek, have you tested this in VS 2008 (Team System, SP1, .NET 3.5 SP1) but on Windows Server 2008 x64?

    I can see the Fields Explorer window, but when I try to enter the site URL, I get an error indicating that the web application at [url] could not be found. I also tried localhost variants, with/without trailing "/", FQDN, you name it.

    I have confirmed that the same URL works in IE, so I know SP is running. I *am* using different ports (I have nothing on port 80); could this be it?

    Right now, I am guessing it's either x64 OS, the port, or something else. Thoughts?

    (Thank you for this great tool. I am anxious to see how much it will speed up my dev.)

  13. Waldek Mastykarz Says:

    @Sherman Woo: thank you for your comment. Haven't checked it yet but will try to give it a look as soon as possible. Will let you know if I find something.

  14. Waldek Mastykarz Says:

    @Sherman Woo: Jeffrey has just had a look at the Fields Explorer Visual Studio 2008 add-in on Windows 2008 (x86 though). It works correctly. Are you trying to open a remote site by any chance?

  15. Sherman Woo Says:

    Hi Waldek, no, everything is local. I just tried installing your tool in my Server 2003 x86 VM, and it works fine. (I know, I changed 2 variables, but I don't have a Server 2008 x86 VM at home.)

    It's worth noting in my Server 2008 x64 VM, I had installed John Holliday's CAML Intellisense tool and Andrew Connell's VS "Root folder" add-in ahead of yours, in case that might have an effect.

    HTH.

  16. Waldek Mastykarz Says:

    @Sherman Woo: Thanks for the details. Unfortunately I don't know if Imtech Fields Explorer has any conflicts with any of the tools you've mentioned. We will check it out and let you know if we find anything.

  17. Oliver Says:

    Thanks for the great tool, already saved me a couple of hours on my dev projects.

    We made it "Pick of the month" on http://www.sharepoint-tools.de

    Oliver

  18. Jeffrey Schmitz Says:

    @Oliver: Thanks for making the tool "Pick of the month" It's nice to see that something you make, is usefull for others. Hopefully future tools from me/us will be just as usefull to you :)

  19. MikeH Says:

    I also encountered the same issue on a 64 bit W2K3 OS.

  20. kunz Says:

    Excellent work! Thanks!

Leave a Reply

Security Code:

WP Theme & Icons by N.Design Studio
Entries RSS Comments RSS
Copyright © 2007 - 2010 Waldek Mastykarz

Creative Commons License