Recent changes to patches

2 part Patch for Draco.net's VSS component

Jeffrey Knight — Mon, 11 Oct 2004 15:31:59 -0000

This patch makes 2 changes to the VSSRepository
component of Draco.NET.

Both address the issue of a large solution with many
project distributed around a VSS repository, not
necessarily mirroring the VSS folder structure.

1) Currently:in Draco.builds.config under
<vss><project>, multiple projects can be specified
using a pipe. For example:
<vss>
<project>$/Solutions/Foo|$/Solutions/Bar</project>
</vss>
The projects must all be on the same line which is
cumbersome for large solutions with many projects. The
first change simply removes /n and /r 's so that a user
can have:
<vss>
<project>
$/Solutions/Foo|
$/Solutions/Bar
</project>
</vss>

2) The name of a project in a VS.NET solution might be
different than the name of the project in VSS. But
Draco's "get latest" from VSS puts the project in the
same folder and the VSS's project folder's name. The
2nd change allows Draco to get latest and optionally
specify the name / path of the folder to *get to*. The
.build syntax will be:
<vss>
<project>
$/Solutions/Foo:myProjects/MyFoo|
$/Solutions/Bar:myProjects/MyBar|
</project>
</vss>
This should also be possible, although it wasn't tested:
<vss>
<project>
$/Solutions/Foo:c:\myProjects/MyFoo|
$/Solutions/Bar:c:\myProjects/MyBar|
</project>
</vss>

This is optional, so everything should be backwards
compabible.

Vault support

Ben Moss — Fri, 23 Jul 2004 16:35:03 -0000

patch against draco 1.5.1657.3017 for command line
vault client support for draco.net

hacked together by following the svn patch and James
Geurts' vault API integration
(http://blogs.biasecurities.com/jim/archive/2004/05/10/501.aspx
) as examples.

added:
\service\scc\VaultRepository.cs

modified:
\service\scc\RepositoryFactory.cs - added
VaultRepository to factory method
\service\config\Config.xsd added types for vault config

[Patch] for VssRepository.cs use Interruptible Process

Michael Ferrante — Tue, 02 Mar 2004 08:05:48 -0000

[Patch] for VssRepository.cs use Interruptible Process
GetModifications was not using the Interruptible Process
model for getting the source safe history.

P4Repository, PvcsRepository, and SvnRepository are
still not using the InterruptibleProcess class, but this
fixes VssRepository to use the process runner.

[Patch] for VssRespository.css ToVssDate

Michael Ferrante — Tue, 02 Mar 2004 07:16:27 -0000

This is another patch to cover vss time formatting issues.

Experimentation suggests that VSS uses the regional
settings for short date and a modified version of the long
time format. VSS uses the long time pattern to
determine whether to format time as 12hr or 24hr. The
choice is based on the first appearance of either an H or
h in the LongTimePattern string. If H appears first, 24hr
time is used. If h appears first, 12hr time is used.

For the rest of the time format, minutes are always mm
and the culture specific time separator is used.

This updates the VssRepository.css class to
accommodate this logic.

Bug 777380

Yves Reynhout — Wed, 25 Feb 2004 00:17:42 -0000

Patch for bug 777380

[Patch] Draco.net built against .Net 1.1 framework, VS2003,

Michael Ferrante — Mon, 09 Feb 2004 20:45:06 -0000

[Patch] Draco.net built against .Net 1.1 framework,
VS2003, NUnit 2.1.4
Here is a patch to have Draco.NET compile under 1.1
NET Framework, Visual Studio 2003, NUnit 2.1.4. Builds
under NAnt 0.84.

Change Summary:

Changes:
-build files changed to provide for 1.1 Net framework
compile
-build file change to use NUnit 2.1.4
-Notifier classes changed to work with new security
requirements of .Net 1.1 for xml transform
-Remoting config files changed to support 1.1 Net
security issues
-Config file loading changed to use standard App.config
file, and use
AppDomain.CurrentDomain.SetupInformation.Configuration
File to load remoting config by default.

Remove:
draco/cli/dracocli.remoting.config
draco/service/draco.exe.template.config

Add:
draco/cli/App.config

Problems:

Unable to resolve this warning which only appears in the
Nant build of the Draco service:
(1,1): warning CS1587: XML comment is not placed on a
valid language element

It apppears for 49 files in the compile. It only appears
on the Draco.exe service and if the initial comment /**
is modified then the warning goes away. Warning does
not appear under Visual Studio 2003.

Affected Files:
draco/service/config/ConfigLoader.cs
draco/service/config/ConfigurationSection.cs
draco/service/notify/CompositeNotifier.cs
draco/service/notify/EmailNotifier.cs
draco/service/notify/FileNotifier.cs
draco/service/notify/HookNotifier.cs
draco/service/notify/INotifier.cs
draco/service/notify/NotifierFactory.cs
draco/service/notify/NullNotifier.cs
draco/service/scc/CvsLogParser.cs
draco/service/scc/CvsModification.cs
draco/service/scc/CvsRepository.cs
draco/service/scc/IRepository.cs
draco/service/scc/LogParserBase.cs
draco/service/scc/Modification.cs
draco/service/scc/P4LogParser.cs
draco/service/scc/P4Modification.cs
draco/service/scc/P4Repository.cs
draco/service/scc/PvcsLogParser.cs
draco/service/scc/PvcsModification.cs
draco/service/scc/PvcsRepository.cs
draco/service/scc/RepositoryFactory.cs
draco/service/scc/SvnLogParser.cs
draco/service/scc/SvnModification.cs
draco/service/scc/SvnRepository.cs
draco/service/scc/VssLogParser.cs
draco/service/scc/VssModification.cs
draco/service/scc/VssRepository.cs
draco/service/tool/BuildToolFactory.cs
draco/service/tool/DevEnvBuildTool.cs
draco/service/tool/IBuildTool.cs
draco/service/tool/NAntBuildTool.cs
draco/service/util/FileTraceListener.cs
draco/service/util/InterruptibleProcess.cs
draco/service/util/MessageFormatter.cs
draco/service/util/ProcessReader.cs
draco/service/util/ProcessRunner.cs
draco/service/util/StartInfo.cs
draco/service/util/StringStreamReader.cs
draco/service/AssemblyInfo.cs
draco/service/BuildCoordinator.cs
draco/service/BuildResult.cs
draco/service/BuildRunner.cs
draco/service/BuildUtil.cs
draco/service/Draco.cs
draco/service/DracoHelper.cs
draco/service/DracoInstaller.cs
draco/service/DracoRemote.cs

[Patch] Draco.OnBuildStatusChanged does null check on wrong

Michael Ferrante — Mon, 09 Feb 2004 17:31:49 -0000

We were experiencing problems using the remoting client
to force a build synchronously, an exception was raised.
We traced the problem to a bad guard condition on the
OnBuildStatusChanged event.

Service\Draco.cs file

From:

protected virtual void OnBuildStatusChanged
(BuildEventArgs e) {
// Broadcaster to all registered clients
if (BuildCompleted != null) {
foreach (BuildStatusChangedEventHandler handler
in BuildStatusChanged.GetInvocationList()) {
try {
handler(e);

To:

protected virtual void OnBuildStatusChanged
(BuildEventArgs e) {
// Broadcaster to all registered clients
if (BuildStatusChanged != null) {
foreach (BuildStatusChangedEventHandler handler
in BuildStatusChanged.GetInvocationList()) {
try {
handler(e);

[Patch] for VssRespository.css ToVssDate function for differ

Michael Ferrante — Mon, 09 Feb 2004 17:29:18 -0000

We had problems with SourceSafe identifying correct
history when the ss.exe was run under an account that
had 24hr time format.

Problem seems to be that Windows RegionalSettings
when customized changes the long time format but not
the short time format. SourceSafe seems to use some
version of the LongTime format for its time, not the
ShortTime. So SS.exe was expecting 24hr format, but
Draco was passing time in 12 hr format.

This correction keeps SS.exe in sync with windows
regional settings.

VssRepository.css

Change From:

private string ToVssDate(DateTime dateTime) {
return dateTime.ToString("d") + ";" +
dateTime.ToString("t"); }

Change To:

private string ToVssDate(DateTime dateTime) {
return dateTime.ToShortDateString() + ";" +
dateTime.ToLongTimeString(); }

Support for DevStudio 2003

Jerry Albro — Thu, 13 Nov 2003 17:07:30 -0000

I have added support for the DevStudio.NET 2003 build
environment. The choice of which DevStudio to use is
made by adding the "edition" attribute to the
<devstudio> element in the draco.exe.config file.

So, using <devenv> will execute DevStudio.NET and using
<devenv edition="2003"> will execute DevStudio.NET 2003.

The attach zip contains the changed files.

Support for rolled back, move to, unpinned

John Theisen — Wed, 16 Jul 2003 06:29:51 -0000

Support was missing for the unpinned and rolled back (I
found the other patch too late!) and move to for VSS. I
am using version 6.0c here.