last day (4717 days later) » 

12:42 PM
Welcome to chat for: SharePoint
This is a general discussion room, but please feel free to create more subject-specific rooms (a single room with every possible discussion isn't very helpful)
For playing with chat features:

Sandbox

Where you can play with chat features (except flagging) and ch...
For feedback:

Chat feedback

Problems with chat? Let us know...
and remember; please read the FAQ ;p)
 
 
3 hours later…
4:07 PM
Hello... no one. Damn.
 
 
1 hour later…
5:13 PM
So... SharePoint?
Wowee!
yes.
I feel so alone!!!
HELLO LO Lo lo o o . . .
 
5:43 PM
...is it me you're looking for?
 
Rename the chat room to the "SharePoint void"
 
lol give it time, it's still day one
 
Man.. it seemed like it took forever to create the site. Now that it is here I don't know what to do!
4
 
Yeah, I've been waiting for SP.SE for a long time now. I'm knee-deep in setting up a SP2010 install for my company right now and I've got a lot of little nagging questions.
 
I need to get SP 2010 setup in VirtualBox. I only have access to 2007 at the moment...
 
5:57 PM
I demo'ed 2007 for a few weeks and I've got to say that 2010 is markedly better, even considering my extremely limited exposure to both.
 
I think development using MSVS 2010 is nicer too. I had the opportunity to take a DEV class and it was pretty cool.
 
I've got VS2010 on my machine and as soon as I can double my RAM and get a license for Win7 Pro x64 I'm going to set up the SP Dev Environment so I can start building my own webparts.
I can't wait. lol
 
I would love to develop for SharePoint 2010, It seems like I am doing a lot of setup and boilerplate code everytime I want to do something in SP2007.
 
You have SharePoint setup on Win7 pro? Was that pretty easy to setup?
 
I love StackOverflow, but it seems like so many approach SP issues without understanding the craziness of SP at all
So WHOO for this site!
 
6:10 PM
Chris, I am very interested to know the answer to your question: sharepoint.stackexchange.com/questions/10840/…
 
Surely someone knows something, it's got me stumped.
 
All of my workflow actions are junked up... they each live in their own Namespace and THEN their own class... I had a hard time getting them working when I first started messing with it and that was the only way I could get it to work.
 
@KitMenke Were you asking me? Because my SP install is on a Win Server 2008 R2 virtual box. I'm going to have to set up the dev environment on my personal workstation.
BTW these chat conversations become a lot easier to follow if we all use the reply arrows :)
 
@JonnyP Yeah I was. I have Win Server 2008 R2 in VirtualBox with WSS 3.0... I didn't want to clutter my Win7 machine
 
My workflow actions are all in the same dll - which is stupid, but easier for me to code. Of course, I also have a dummy dll used just for the deployment since I am using VSSEWSS. I wish there was an easy way to add a dependency on a class library that would deploy if missing, but NOT retract if others are dependent on it. Learned that one the hard way
 
6:15 PM
@theChrisKent Yeah all of my actions/conditions are in the same DLL too. I have a static class in there too that I put all the shared functions in (ex: logging to history list).
 
@KitMenke We're actually migrating all of our servers to VMs (using VSphere) and this SharePoint install I'm dealing with is brand new for us. It's replacing an aging and open-source intranet and most of our file server.
 

  last day (4717 days later) »