VSeWSS 1.2 (enabling 64bit support)

rated by 0 users
This post has 21 Replies | 7 Followers

Top 200 Contributor
Posts 7
Points 161
JohnMcBride Posted: Mon, Jun 16 2008 12:19 PM

 I'm sure everybody has already is aware that MS released VSeWSS 1.2 with support for VS 2008. The only problem with this is that it doesnt support installing on 64 bit operating systems.

[insert your own soap box entry here] :)

Since bamboo's vista install for WSS/MOSS was helpful to me I wanted to post something here ther will hopefully help 64bit developers out.

If you want to get the extensions installed on 64 bit OS's check out my blog post here for detailed instructions and screenshots.

http://www.sharepoint-stuff.com/?p=54

Hope this helps

John McBride
www.sharepoint-stuf.com

Top 10 Contributor
Posts 509
Points 14,327

John,

Thanks for posting the solution here! I will try it ASAP since I'm running 64bit Vista.

Thanks again!

/Jonas

Top 150 Contributor
Posts 9
Points 232
Kevster replied on Sun, Jun 29 2008 12:45 AM

Doesn't work for me - the installer stops with "The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2356."

I'm running Vista 64 + VS2008, SharePoint not installed.

Top 10 Contributor
Posts 509
Points 14,327

Kevster,

Error 2356 means"Couldn't locate cabinet in stream: [2]."

Take a look at this post http://blogs.msdn.com/windows_installer_team/archive/2005/08/20/451532.aspx

For a reference to msi error go here http://desktopengineer.com/msierrors

You probably have to rebuild the msi again.

/Jonas

Top 150 Contributor
Posts 9
Points 232
Kevster replied on Sun, Jun 29 2008 12:57 PM

 Jonas -

Did you get it to work? I opened the extracted .msi (which also produced a 'Catalog' folder in the extracted dir) in Orca and I saved it back just like the instructions said. I'm thinking that saving it is not including the 'Catalog' folder but I'm not sure.

Kevster

Top 10 Contributor
Posts 509
Points 14,327

Kevster,

I have actually not tried it yet, so I can't help much.

/Jonas

Top 200 Contributor
Posts 7
Points 161

Kevster,

I noticed that you do not have WSS installed when when trying to run the patched msi for the VSeWSS extensions. To be honest I have not tried this scenerio, as this was meant to follow up bamboo's solution of installing WSS/MOSS on a vista OS. The assumption is that WSS is installed.

If you take a look at the post one of the keys we are deleting using the ORCA tool, is the "WssNotInstalled" key, which enables you to run it even when WSS is not installed.

I would try installing WSS Sp1 and then try the patch'd MSI again and i am pretty confident that it will work.

Please let me know if i can do anythin to help.

 

John

Top 150 Contributor
Posts 9
Points 232
Kevster replied on Sun, Jun 29 2008 11:31 PM

Actually I thought about that so I installed WSS but I still get that 2356 error code as soon as it gets to "copying files..."

Top 200 Contributor
Posts 7
Points 161

 Kevster,

Ok, I have seen that error 2356 when using ORCA you try to do a "Save As" to save the MSI to something different. Are you doing a Save As and saving the modified MSI to a different name, or are you just doing a Save to directly save back into the editing MSI?

Let me know

John

Top 150 Contributor
Posts 9
Points 232
Kevster replied on Mon, Jun 30 2008 10:19 AM

John,

After running the /extract, I get a c:\extractedvse directory with the following:

- vsewssv12.msi

- Catalog folder

   - files12.cat (inside Catalog folder)

 

After deleting the keys, I save as vsewssv12.msi to a different folder and try executing it.

Top 200 Contributor
Posts 7
Points 161

 Kevster,

You will need to just execute the Save menu option with ORCA. If you try to save as to a different filename or directory, ORCA loses some information from the MSI. Just try the save option directly and that should work.

John

Top 150 Contributor
Posts 9
Points 232
Kevster replied on Mon, Jun 30 2008 12:31 PM

 John -

Thanks. Saving it to the same file seemed to work.

I'll let you know how all else goes.

- Kevster

Top 200 Contributor
Posts 7
Points 161

 Kevster,

No problem, Glad it worked for you. Just remember that i havent tested the things like deploy and stuff from within the extensions

John

Top 150 Contributor
Posts 9
Points 232
Kevster replied on Tue, Jul 1 2008 6:39 AM

JohnMcBride:

 Kevster,

No problem, Glad it worked for you. Just remember that i havent tested the things like deploy and stuff from within the extensions

John

 

 It appears deployment is where the problem arises - getting "object reference not set to an instance of an object" - no trace information. It would've been nice though.

Not Ranked
Posts 1
Points 5

This is my first time posting to this blog but have been reading for quite a while.

I also eagerly modified my msi file in order to install on 64 bit (Win 2003 64 bit, VS 2008, VSeWSS 1.2, MOSS 2007 64 bit).

Every feature / function of WSeWSS seems to work except the .wsp file and the setup.bat file are never added...

Does anyone have any thoughts / experience on how to resolve this issue?
Note: In the mean time I am using community tools like WSPBuilder which seems to have no trouble working on 64 bit....

Error:

------ Deploy started: Project: DataEntryApp, Configuration: Debug Any CPU ------

System.NullReferenceException

Server Error: Object reference not set to an instance of an object.

 

Page 1 of 2 (22 items) 1 2 Next > | RSS
Bamboo Solutions Corporation, 2002-2012