I have used this blog entry but only for customising the look and feel of a
list item
http://office.microsoft.com/en-us/sharepointdesigner/HA10119033.aspx
From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of
Jeremy Thake
Sent: Wednesday, 20 January 2010 1:53 PM
T
Have you ensured you are using SP2 of SPD? That made a little more bearable.
Otherwise you're in the realm of reverse engineering List Templates (using
SPSource or Solution Generator) and deploying them back via a WSP. That way you
can edit them in Visual Studio as .aspx files rather than using
Must be costing you a fortune in bandwidth everytime someone replies...
From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of
David Connors
Sent: Wednesday, 20 January 2010 4:40 PM
To: ozMOSS
Subject: Re: Outlook 2010 Message Bloat
2010/1/20 Paul Noone
And lose that se
2010/1/20 Paul Noone
> And lose that sexy Build On footer? No way! ;)
>
> With regards to the CSS it all appears related to list styles and about
> 99.9% of it is redundant bloat.
>
> I'd hate to go down the plain text path and try to portray my screenshots
> as ASCII art.
Agree (thanks for the
Hi All
I looking for good blogs / info on creating and editing list Forms. SPD really
sucks with creating a form for a list. Are there any other tools you might
recommend?
Regards,
Marko
This email and any files transmitted with it are intended solely for the use of
the individual or entity
Hi all
Been stumped on this one for a while so thought i'd try my chances here. Now
the CQWP is much improved, and it's almost doing the trick.
>From reading this page:
http://technet.microsoft.com/en-us/library/ee721053(office.14).aspx it
indicates that the CQWP can be used for large page librar
And lose that sexy Build On footer? No way! ;)
With regards to the CSS it all appears related to list styles and about 99.9%
of it is redundant bloat.
I'd hate to go down the plain text path and try to portray my screenshots as
ASCII art.
-Original Message-
From: ozmoss-boun...@ozmoss.
Hi David,
In the interim – is there something we can do to ease things? Change over to
text perhaps for this list and others?
From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of
David Connors
Sent: Wednesday, 20 January 2010 3:17 PM
To: ozMOSS
Subjec
I will keep it agnostic where possible, but will give examples on both for
context. I appreciate that not everyone will be jumping on SP2010 straight away
and I want to try and get the message out. It scares me how many places don't
use source control, let alone using a build server to produce t
Cool Jeremy. Is the presentation focused toward SP 2007/2010 or neither
in particular?
C
From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On
Behalf Of Jeremy Thake
Sent: Wednesday, 20 January 2010 11:28 AM
To: ozMOSS
Subject: RE: Source Control for VS Projects
+
+1 to TFS. Also remember that TFS 2010 (RTM in April) will have a Basic Edition
which is a lot more affordable than the full TFS 2010 suite.
I am presenting on TFS + SharePoint Dev at the ALM conference in Sydney in
April, they'll be plenty of content on the SharePointDevWiki.com around this
so
+1 TFS. As a relatively inexperienced developer, TFS (2008) has been
pretty easy to jump into to manage SP projects. Work item tracking and
linking to source changes is brilliant TFS or other. But my only
experience is with TFS and I'm always happy to work with it.
C
From: ozmoss-boun...
+1 to Subversion w/ Tortoise and Ankh.
Tortoise adds awesome desktop integration and control, while Ankh provides a
subset of this functionality from within VS. I've run into a few branching
issues and conflicts when using both but nothing insurmountable.
Fig.1 - Desktop integration with Tortoi
They've simplified a fair bit of stuff with TFS 2010 which should make it
easier to run and manage. Bear in mind that, if you go down another path for
tooling that you don't get the integration that you get with TFS/VSTS. For
example, here's a blog post that I wrote yesterday:
http://201
SVN with Tortoise and Ankh all the way - only had heartache and pain with boths
VSS and TFS
Cheers,
Nige
From: dan...@danielbrown.id.au
To: ozmoss@ozmoss.com
Date: Tue, 19 Jan 2010 23:03:10 +1030
Subject: RE: Source Control for VS Projects
Team Foundation Server is nice, but very bi
Yep, steer clear of VSS. It's both cumbersome and also beyond the end of its
lifetime. Two of the better source control systems that I see in wide use
today are SubVersion and TFS.
The good thing about SubVersion is that it's free and has some really good GUI
tools (e.g. TortoiseSVN) for co
Team Foundation Server is nice, but very big and heavy if it's a small dev team.
A great alternative which I've had some success with is SVN.
From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of
Power, Karl
Sent: Tuesday, 19 January 2010 10:48 PM
To: ozmoss@ozmoss.com
Hi folks,
I was wondering what tools are being used by some of you guys for
managing source code? We were looking at deploying SourceSafe but we
have come across some pretty scathing reviews. Any information would be
greatly appreciated,
Rgds,
KP
Karl Power
Glanbia Business Services
Gl
18 matches
Mail list logo
