tchmiel's blog - All Comments

re: wssv3SP1 install: "This product requires ASP.NET v2.0" error

007 — Wed, 05 Nov 2008 12:54:45 GMT

Thanks for this post! Same problem --> fix worked fine!

Posted on SharePoint Blogs

re: wssv3SP1 install: "This product requires ASP.NET v2.0" error

Suresh — Tue, 04 Nov 2008 11:09:59 GMT

Thanx for your helpful information.

Posted on SharePoint Blogs

re: wssv3SP1 install: "This product requires ASP.NET v2.0" error

Francisco — Mon, 27 Oct 2008 15:01:15 GMT

Beautiful man. some many other forum have you running around in circle. this answer worked and it was straight to the point

Posted on SharePoint Blogs

re: wssv3SP1 install: "This product requires ASP.NET v2.0" error

Will — Wed, 22 Oct 2008 20:57:51 GMT

Thanks for this post I was almost stumped!

Posted on SharePoint Blogs

re: wssv3SP1 install: "This product requires ASP.NET v2.0" error

Bharat — Mon, 13 Oct 2008 14:48:50 GMT

Thanks! It worked for me. Lovely.

Posted on SharePoint Blogs

bloggingIT » Blog Archive » Trouble installing Sharepoint on a fresh Windows Server 2003 SP2

Sun, 14 Sep 2008 20:12:31 GMT

Pingback from bloggingIT » Blog Archive » Trouble installing Sharepoint on a fresh Windows Server 2003 SP2

Posted on SharePoint Blogs

re: wssv3SP1 install: "This product requires ASP.NET v2.0" error

Simon Boigelot — Sat, 05 Jul 2008 17:33:24 GMT

Great, it worked for me too ;)

Posted on SharePoint Blogs

re: wssv3SP1 install: "This product requires ASP.NET v2.0" error

Louis-P — Wed, 18 Jun 2008 19:10:03 GMT

Thanks a lot!!!!!

Posted on SharePoint Blogs

re: Custom Content Types with Custom Icons

tchmiel — Wed, 04 Jun 2008 20:59:17 GMT

@Brian,

No, not really. My guess is that you would create a custom view using CAML and then conditional display a icon based on its content type. If you can't determine the content type via CAML, you could create a hidden column where each content type has a unique value, and the conditional check in CAML. You could store the icons in a doc library on the site, and refer to them via relative path.

Posted on SharePoint Blogs

re: Custom Content Types with Custom Icons

tchmiel — Thu, 27 Mar 2008 13:44:14 GMT

@Casey

take at look at

www.codeplex.com/sharepad

This is where we started from. This is based on Sharepoint 2003 interfaces and has not been updated to support the 2007 interfaces.

Posted on SharePoint Blogs

re: Custom Content Types with Custom Icons

Casey Hanks — Thu, 27 Mar 2008 13:09:21 GMT

From your article I am hoping that you might have some experience with creating a custom version of the SharePoint.OpenDocuments ActiveX control

This article gives hints about how to accomplish this:

msdn2.microsoft.com/.../aa978104.aspx (tells how to do everything except created the custom ActiveX control)

Do you have sample code showing an ActiveX control that implements the interfaces of the SharePoint.OpenDocuments class

Thanks,

Casey Hanks

c.hanks@InfoAssure.net

(443) 837-2221

Posted on SharePoint Blogs

re: wssv3SP1 install: "This product requires ASP.NET v2.0" error

France — Wed, 20 Feb 2008 15:25:27 GMT

Hi Tom,

Thanks a lot. I have the same problem for several days now. I found your blog, applied your tip and it works! Thank you so much for taking the time to write this solution and for caring to help others.

Posted on SharePoint Blogs

re: How to upgrade a custom wssv2 site definition to wssv3 default team site

john — Fri, 15 Feb 2008 17:25:58 GMT

OK, solved it!

I had to edit the CustomWSSUpgrade.xml file to include file paths from the default site definitions as well as our custom site definitions and rename the WSSUpgrade.xml so it would not be read by the migration engine. Since the WebTemplateID was the same in both files, the custom one took precedence and the default was never used for mappings.

Posted on SharePoint Blogs

re: How to upgrade a custom wssv2 site definition to wssv3 default team site

john — Tue, 05 Feb 2008 15:20:48 GMT

Ran through option 2. This resets the site to V2 look/feel. Revert to site definition does not correct. I do not have the option to "Revert to Template"

Posted on SharePoint Blogs

re: How to upgrade a custom wssv2 site definition to wssv3 default team site

john — Tue, 05 Feb 2008 13:19:44 GMT

The V2 sites rendered fine after the change, it was when I migrated them that they wouldn't render in V3. Will try option 2 for V3 sites today. Smigrate has some success in correcting the issues I'm seeing. Still experimenting.

Posted on SharePoint Blogs

re: How to upgrade a custom wssv2 site definition to wssv3 default team site

tchmiel — Mon, 04 Feb 2008 22:14:49 GMT

@John,

Did you try step #2 again?

Posted on SharePoint Blogs

re: How to upgrade a custom wssv2 site definition to wssv3 default team site

john — Mon, 04 Feb 2008 21:52:24 GMT

Tried this and it worked very well. A couple of caveats that I ran into. We had sites that used ID "1" as well as custom sites that we changed to "1". The custom sites came over, the default ones did not. Still looking into this

Posted on SharePoint Blogs

re: How to upgrade a custom wssv2 site definition to wssv3 default team site

Kevin — Thu, 24 Jan 2008 16:19:13 GMT

I actually modified the site definition. I made a copy of the default team site template and modified the index.aspx to replace the left quick launch bar by a zone so i can add custom menu. it wasn't heavy customized at all

is step 2 required if my homepage is not corrupted?

I'm doing this on our dev server and both wss 2.0 and moss are clean installation :)

do you have any other ideas?

thanks.

Posted on SharePoint Blogs

re: How to upgrade a custom wssv2 site definition to wssv3 default team site

tchmiel — Thu, 24 Jan 2008 02:29:11 GMT

@Kevin,

How customized is your site template?

Did you check the log files for any errors?

Did you try resetting iis? Try Step #2 above?

Since both ways failed, sounds like you might have a dependency that does not exist in the wssv3.

In our experience, this upgrade process is a fragile process and only works when the everything aligns.

Sorrry can't be more help.

- Tom

Posted on SharePoint Blogs

re: How to upgrade a custom wssv2 site definition to wssv3 default team site

Kevin — Thu, 24 Jan 2008 00:18:17 GMT

I tried both method but nothing work.

first i tried reverting custom site template to 1 and upgrade the site from central admin / operation and the custom site didn't get upgrade to moss template

i also tried Frank's method of creating a copy of MOSS TST and assign the same ID as the custom site definition, then run the upgrade but the site still look like sharepoint 2003

any ideas?

Posted on SharePoint Blogs

Windows Update » Bizarre CHM file bug

Windows Update » Bizarre CHM file bug — Sat, 29 Dec 2007 21:01:11 GMT

Pingback from Windows Update » Bizarre CHM file bug

Posted on SharePoint Blogs

re: wssv3SP1 install: "This product requires ASP.NET v2.0" error

Shaun Jones — Fri, 28 Dec 2007 19:17:27 GMT

Beautiful ...... Same situation....... same problem...... same fix worked for me.

Thanks!

Posted on SharePoint Blogs

Windows Update » wssv3SP1 install: "This product requires ASP.NET v2.0" error

Windows Update » wssv3SP1 install: "This product requires ASP.NET v2.0" error — Fri, 28 Dec 2007 03:48:33 GMT

Pingback from Windows Update » wssv3SP1 install: "This product requires ASP.NET v2.0" error

Posted on SharePoint Blogs

re: Custom Content Types with Custom Icons

tchmiel — Thu, 29 Nov 2007 23:35:59 GMT

@EddieV - Sorry, I have never seen this behavior before. Sounds like a page caching problem. Sorry I can't really help. Have you tried creating a new site after the icons are installed, and do you still have the problem there?

Posted on SharePoint Blogs

re: Custom Content Types with Custom Icons

EddieV — Wed, 28 Nov 2007 15:01:06 GMT

Hello

I have all my icons displaying in my document libraries and i got the pdf icon to work as well, but everyday i have to reset IIS 6 to have the icons reappear. Do you know what might be causing this and how do i correct this?

Thank you

Posted on SharePoint Blogs