---
Bugs:

According to the SF trackers we are now down to 8 bugs, two of them
are sufficiently critical enough that they have to be fixed before a
new release can go out. These two bugs are:

SF1677584 "Cannot explicitly exclude categories for test run": Here we
need to extend the UI and the underlying logic so that it becomes
possible to explicitly state which categories should be excluded. The
resulting logic would then be that a test is run if it Included and
Not Excluded at the same time. The third state for a category can then
be "Don't Care" which means it will not be run if not included, but it
doesn't have to explicitly excluded. Note that all category settings
will be stored in the recipe, and the command line will read and apply
those settings as well.
We are currently working on this as not fixing it would mean that we
would remove existing functionality. In this case we don't want to do
that.

SF1680425 "Test hierarchy doesn't report location of failed
assertion": Just reporting a failed test is not sufficient. Each user
would like to have sufficient information about where it failed. This
bug, too, must be fixed before the next release.

---
New Features:

The next release will see an additional feature: the TestAttribute
will support an additional optional named parameter for a Timeout.
Here a user can specify the timeout in milliseconds and if the test
doesn't finish within that time, it will be reported as failed.

---

Timeline:
It all depends on how fast we can get the two above mentioned bugs
fixed. We are still shooting for March 31, but it has to go very well.


Thank you to all the people who provide feedback for your support!

Kind regards,
Manfred.
---
Manfred Lange.
csUnit team member
http://www.csunit.org

For the command line version of csUnit currently the two options
supported are testCategory and fixtureCategory.

The questions I have are:

1) Can you provide with with examples of how you use the command line
with these options?

2) Also, if there was a possibility to improve these options, what
would your suggestion be?

Currently we plan to make these two options obsolete and replace them
by a single "categories" option. In a first step the only way to use
it is to specify one or more categories which must be matched by
either the test, or in absence on the test level, the category of the
fixture.

I'd like to invite you to share your thoughts. Thank you!

Kind regards,
Manfred.
---
Manfred Lange.
csUnit developer

Hi,

we have just discovered that it is possible to mark more than one
method within a test fixture with the attributes SetUp (or TearDown)
respectively.

If a test fixture has a lot of tests in it, it is well possible to
accidentally have more than one setup/teardown method.

We think it would be useful to give the user feedback that this has
happened, but we are unsure about what the best option would be.

An output on the console (output tab in the GUI) allows continuing the
test execution, but can easily overlooked.

Failing all associated tests on the other hand might be a bit too
harsh, although we tend to prefer this solution. The sooner a error is
detected, including defects in tests, the smaller the possible damage.

In case you have preference we would like to hear about it. Thank you!

Kind regards,
Manfred.
---
Manfred Lange.
csUnit team member

Hi all,

at this stage we have finished most of the work at the GUI. This also
included the interaction between the core, csUnit's UI controls, and
the graphical UI (csUnitRunner).

Next, we will turn to the command line. Admittedly this wasn't one of
the strengths of csUnit in the past. This is also reflected by the
small number of tests we have in that space.

As both the command line and the GUI runner share the same core, we
don't expect significant changes in the core. Handling of multiple
categories is now solid, and category selections are even stored in
the recipe.

Basically the GUI runner is evolving more and more into an editing
tool for recipes while at the same time keeping all features to
execute test suites. In contrast the command line won't see additional
options as it is merely an executor for recipes or assemblies.
Settings for additional features and their settings would therefore
generally be found in the recipe.

After the command line, we will also revisit the VS2005 add-in, but we
might create a new release before that.

Kind regards,
Manfred.
---
Manfred Lange.
csUnit team member

Hi all,

the changes required to support multiple categories at the test
fixture and test method level are more or less complete. Several
refactorings have led to simpler and at times slightly faster code.
Once in a while we profile the code with DotTrace from JetBrains.
Also, we introduced several new internal interface to improve
testability and testing speed. The UI for the categories selection has
change in that it is now possible to select more than one category.
Also the UI no longer distinguished between test fixture categories
and test method categories. This made it much simpler.

While the head revision is very stable we are aware of several areas
in the code that deserves more refactoring. We haven't decided yet,
however, which of these we will do for the next version, and which we
will move to later.

At this stage we are aware of four open and known issues which we
would like to fix before we make a new built available. Furthermore,
we received a few code submissions which we would like to consider for
inclusion as well.

The recent work has focused largely on csUnitRunner, the stand-alone
GUI runner. However, most of the functionality is contained in a
control which is also used for the VisualStudio addin. Therefore
allmost all improvements will be available in both scenarios.

We haven't done a lot of work on the csUnitCmd, though. We think it
might be of value to make a new build available first, and then to
also put some more work into csUnitCmd.

I thought it might be valuable to share this information with you. In
terms of time frames it is now looking more likely that a new version
will become available in March. However, as always the head revision
in the CVS at SourceForge has the latest set of source. Keep in mind,
though, that it represents work in progress and is therefore unsupported.

Kind regards,
Manfred.
---
Manfred Lange.
csUnit team member

Ah... I have the 2.11 beta and it didn't work for me for some reason...

  Amir Kolsky
XP& Software



   _____

From: csunit@yahoogroups.com [mailto:csunit@yahoogroups.com] On Behalf Of
manfred_lange_agile
Sent: Friday, February 09, 2007 7:00 AM
To: csunit@yahoogroups.com
Subject: [csunit] Re: An Update



Amir,

no worries! The behavior with regards to that has not changed.

Instead the categories concept is implemented in such a way that if
you don't want to use it you don't have to change anything in your
existing tests.

As for the tests: Either use the naming convention or decorate them
with the [Test] attribute. Similarly for the setup and teardown
methods: either use the convention to name them Setup or TearDown or
use the attributes [SetUp] or [TearDown]. You can even mix the
different styles.

As for the test fixtures: Either use a name ending in test, or use the
[TestFixture] attribute. Again, within an assembly you can mix both
styles.

Does this answer help?

Kind regards,
Manfred.
---
Manfred Lange.
csUnit team member

--- In csunit@yahoogroups. <mailto:csunit%40yahoogroups.com> com, "Amir
Kolsky" <kolsky@...> wrote:
>
> Do you now require a test attribute on each an every method and test
class?
>
> Amir Kolsky
> XP& Software
>
>
>
> _____
>
> From: csunit@yahoogroups. <mailto:csunit%40yahoogroups.com> com
[mailto:csunit@yahoogroups. <mailto:csunit%40yahoogroups.com> com] On
Behalf Of
> manfred_lange_agile
> Sent: Tuesday, February 06, 2007 11:40 PM
> To: csunit@yahoogroups. <mailto:csunit%40yahoogroups.com> com
> Subject: [csunit] An Update
>
>
>
> Hi all,
>
> after some time of silence I'd like to give you a few details of what
> we are currently doing with csUnit.
>
> Work has not stopped! Instead we are working on making categories more
> powerful, and as a consequence we have discovered interesting new
> concepts which we want to build out better through refactoring.
>
> At this stage we are also adding more and more tests. The functional
> footprint is not expanded right now. Instead we focus on quality and
> simplicity. More than once a simpler implementation has led to small
> performance improvements.
>
> If you want to work with the latest and greatest version of the code
> base, you can use SourceForge's CVS repository. You can get the latest
> version of the code base from there. Please note, that this is always
> a development snapshot and not a supported release. We plan to have a
> supported release again soon.
>
> Kind regards,
> Manfred.
> ---
> Manfred Lange.
> csUnit team member
>
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>







[Non-text portions of this message have been removed]

Amir,

no worries! The behavior with regards to that has not changed.

Instead the categories concept is implemented in such a way that if
you don't want to use it you don't have to change anything in your
existing tests.

As for the tests: Either use the naming convention or decorate them
with the [Test] attribute. Similarly for the setup and teardown
methods: either use the convention to name them Setup or TearDown or
use the attributes [SetUp] or [TearDown]. You can even mix the
different styles.

As for the test fixtures: Either use a name ending in test, or use the
[TestFixture] attribute. Again, within an assembly you can mix both
styles.

Does this answer help?

Kind regards,
Manfred.
---
Manfred Lange.
csUnit team member

--- In csunit@yahoogroups.com, "Amir Kolsky" <kolsky@...> wrote:
>
> Do you now require a test attribute on each an every method and test
class?
>
>  Amir Kolsky
> XP& Software
>
>
>
>   _____
>
> From: csunit@yahoogroups.com [mailto:csunit@yahoogroups.com] On
Behalf Of
> manfred_lange_agile
> Sent: Tuesday, February 06, 2007 11:40 PM
> To: csunit@yahoogroups.com
> Subject: [csunit] An Update
>
>
>
> Hi all,
>
> after some time of silence I'd like to give you a few details of what
> we are currently doing with csUnit.
>
> Work has not stopped! Instead we are working on making categories more
> powerful, and as a consequence we have discovered interesting new
> concepts which we want to build out better through refactoring.
>
> At this stage we are also adding more and more tests. The functional
> footprint is not expanded right now. Instead we focus on quality and
> simplicity. More than once a simpler implementation has led to small
> performance improvements.
>
> If you want to work with the latest and greatest version of the code
> base, you can use SourceForge's CVS repository. You can get the latest
> version of the code base from there. Please note, that this is always
> a development snapshot and not a supported release. We plan to have a
> supported release again soon.
>
> Kind regards,
> Manfred.
> ---
> Manfred Lange.
> csUnit team member
>
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>

Do you now require a test attribute on each an every method and test class?

  Amir Kolsky
XP& Software



   _____

From: csunit@yahoogroups.com [mailto:csunit@yahoogroups.com] On Behalf Of
manfred_lange_agile
Sent: Tuesday, February 06, 2007 11:40 PM
To: csunit@yahoogroups.com
Subject: [csunit] An Update



Hi all,

after some time of silence I'd like to give you a few details of what
we are currently doing with csUnit.

Work has not stopped! Instead we are working on making categories more
powerful, and as a consequence we have discovered interesting new
concepts which we want to build out better through refactoring.

At this stage we are also adding more and more tests. The functional
footprint is not expanded right now. Instead we focus on quality and
simplicity. More than once a simpler implementation has led to small
performance improvements.

If you want to work with the latest and greatest version of the code
base, you can use SourceForge's CVS repository. You can get the latest
version of the code base from there. Please note, that this is always
a development snapshot and not a supported release. We plan to have a
supported release again soon.

Kind regards,
Manfred.
---
Manfred Lange.
csUnit team member







[Non-text portions of this message have been removed]

Hi all,

after some time of silence I'd like to give you a few details of what
we are currently doing with csUnit.

Work has not stopped! Instead we are working on making categories more
powerful, and as a consequence we have discovered interesting new
concepts which we want to build out better through refactoring.

At this stage we are also adding more and more tests. The functional
footprint is not expanded right now. Instead we focus on quality and
simplicity. More than once a simpler implementation has led to small
performance improvements.

If you want to work with the latest and greatest version of the code
base, you can use SourceForge's CVS repository. You can get the latest
version of the code base from there. Please note, that this is always
a development snapshot and not a supported release. We plan to have a
supported release again soon.

Kind regards,
Manfred.
---
Manfred Lange.
csUnit team member

Using CSUNit 2.1.1 beta with VS 2005, .NET 2.0, .NET CF 2.0.

Following the tutorial at
http://www.csunit.org/tutorials/tutorial8/step5.html

CSUNit GUI looks different, no File, View, etc. menu.
Progress bar is 0%, starting the test (using the Calculator example),
progress bar stays at 0%.
But it should failed.

Please assist in solving this

  :-(

Manfred, I have sent you in the past my csUnit version with the /test,
/fixture and /namespace additions. It takes care of this requests...

  Amir Kolsky
XP& Software


>-----Original Message-----
>From: csunit@yahoogroups.com [mailto:csunit@yahoogroups.com]
>On Behalf Of Hugh Beyer
>Sent: Monday, August 28, 2006 6:53 PM
>To: csunit@yahoogroups.com
>Subject: [csunit] Re: Can I debug just one test?
>
>Bump. If it's not possible, I'd like to know and I'll make a
>feature request.
>
>--- In csunit@yahoogroups.com
><mailto:csunit%40yahoogroups.com> , "Hugh Beyer" <beyer@...> wrote:
>>
>> I just got started using csUnit in my visual basic .net project, and
>> it's great (Visual Studio 2005). Only thing is I can't
>figure out how
>> to debug just one test. I can use csUnitRunner, which lets me choose
>> the test but not debug; or I can use F5 (after setting my
>test project
>> as the startup project) and debug all my tests. But if I'm
>working on
>> one failing test there isn't an easy way to run just that one, that
>I see.
>>
>> Right now I'm using the <ignore> attribute on all the test fixtures
>> I'm NOT working on, but that's kludgey--I have to go edit a bunch of
>> test files. Is there a better way?
>>
>> Hugh
>>
>
>
>
>

Also, if you install ReSharper (www.jetbrains.com) you will be able to use
the ReSharper test runner to debug a single test. All you need to do is
right click on the gutter where the test icon sits and select "debug test".

  Amir Kolsky
XP& Software



   _____

From: csunit@yahoogroups.com [mailto:csunit@yahoogroups.com] On Behalf Of
Hugh Beyer
Sent: Monday, August 28, 2006 6:53 PM
To: csunit@yahoogroups.com
Subject: [csunit] Re: Can I debug just one test?



Bump. If it's not possible, I'd like to know and I'll make a feature
request.

--- In csunit@yahoogroups. <mailto:csunit%40yahoogroups.com> com, "Hugh
Beyer" <beyer@...> wrote:
>
> I just got started using csUnit in my visual basic .net project, and
> it's great (Visual Studio 2005). Only thing is I can't figure out how
> to debug just one test. I can use csUnitRunner, which lets me choose
> the test but not debug; or I can use F5 (after setting my test project
> as the startup project) and debug all my tests. But if I'm working on
> one failing test there isn't an easy way to run just that one, that
I see.
>
> Right now I'm using the <ignore> attribute on all the test fixtures
> I'm NOT working on, but that's kludgey--I have to go edit a bunch of
> test files. Is there a better way?
>
> Hugh
>







[Non-text portions of this message have been removed]

Bump. If it's not possible, I'd like to know and I'll make a feature
request.

--- In csunit@yahoogroups.com, "Hugh Beyer" <beyer@...> wrote:
>
> I just got started using csUnit in my visual basic .net project, and
> it's great (Visual Studio 2005). Only thing is I can't figure out how
> to debug just one test. I can use csUnitRunner, which lets me choose
> the test but not debug; or I can use F5 (after setting my test project
> as the startup project) and debug all my tests. But if I'm working on
> one failing test there isn't an easy way to run just that one, that
I see.
>
> Right now I'm using the <ignore> attribute on all the test fixtures
> I'm NOT working on, but that's kludgey--I have to go edit a bunch of
> test files. Is there a better way?
>
> Hugh
>

I'm just a watcher of this group, not a user of the software (now), so I didn't
think it was right to chime on this in until someone expressed what I was
thinking.

I agree 100% that the points below are all valid.  In particular, the fact that
there's a new way to do something that's different from the old way doesn't mean
that you should force everyone to do it the new way.

Suppose it became _illegal_ in C# to define named methods that are _only_ used
as the target of a delegate, when it's possible in C# v2 to use an "anonymous
method" to avoid the burden of defining a method that's not strictly needed
because of the new feature?  How much outcry would there be?  How is this any
different?

At 02:22 AM 8/24/2006, Amir Kolsky wrote
>No, please don't.
>
>Firstly, we have tons and tons of tests that use the naming convention
>method.
>
>Secondly, we have assemblies that are generated on the fly with tests in
>them that use the naming convention.
>
>Thirdly, we much prefer to ignore tests by adding an 'x' to the method's
>name than by using the ignore attribute as it leaves an ugly stain in the
>output screen.
>
>Fourthly - it requires less code to achieve the same effect - the rule is
>very simple so it is easy to follow. It's so simple, that we have yet to
>need to use the naming attributes. The fact that the language allows you to
>do it does not mean you should... Being manfred_lange_agile, simpliciy
>should be very high on the top of your prioirities :-)
>
> Amir Kolsky
>XP& Software
>
>
>
>  _____
>
>From: csunit@yahoogroups.com [mailto:csunit@yahoogroups.com] On Behalf Of
>manfred_lange_agile
>Sent: Wednesday, August 23, 2006 12:50 PM
>To: csunit@yahoogroups.com
>Subject: [csunit] Proposal: Discontinue support for detecting tests and
>fixtures based on naming c
>
>
>
>Hi,
>
>we are considering to drop csUnit's support for finding Tests and
>TestFixtures based on naming conventions, e.g. fixture names end with
>Test and tests starting with Test.
>
>Instead I'd like to change the specification so that it becomes a
>requirement to use attributes, e.g. TestFixtureAttribute and
>TestAttribute, to mark fixtures and tests.
>
>The benefits would be simplified code with less options for defects.
>Also, use of csUnit would be more consistent with
>TestAssemblyFixtureAttribute etc.
>
>The impact would be that all test fixtures and all tests that still
>rely on naming convention would have to augmented by assigning the
>TestFixtureAttribute to all fixtures and TestAttribute to all tests.
>Depending on the number of tests this might a substantial work.
>
>Please sent your feedback and comments to manfred at csunit dot org.
>Thank you!
>
>Kind regards,
>Manfred.
>---
>Manfred Lange
>co-author csUnit


J. Merrill / Analytical Software Corp

No, please don't.

Firstly, we have tons and tons of tests that use the naming convention
method.

Secondly, we have assemblies that are generated on the fly with tests in
them that use the naming convention.

Thirdly, we much prefer to ignore tests by adding an 'x' to the method's
name than by using the ignore attribute as it leaves an ugly stain in the
output screen.

Fourthly - it requires less code to achieve the same effect - the rule is
very simple so it is easy to follow. It's so simple, that we have yet to
need to use the naming attributes. The fact that the language allows you to
do it does not mean you should... Being manfred_lange_agile, simpliciy
should be very high on the top of your prioirities :-)

  Amir Kolsky
XP& Software



   _____

From: csunit@yahoogroups.com [mailto:csunit@yahoogroups.com] On Behalf Of
manfred_lange_agile
Sent: Wednesday, August 23, 2006 12:50 PM
To: csunit@yahoogroups.com
Subject: [csunit] Proposal: Discontinue support for detecting tests and
fixtures based on naming c



Hi,

we are considering to drop csUnit's support for finding Tests and
TestFixtures based on naming conventions, e.g. fixture names end with
Test and tests starting with Test.

Instead I'd like to change the specification so that it becomes a
requirement to use attributes, e.g. TestFixtureAttribute and
TestAttribute, to mark fixtures and tests.

The benefits would be simplified code with less options for defects.
Also, use of csUnit would be more consistent with
TestAssemblyFixtureAttribute etc.

The impact would be that all test fixtures and all tests that still
rely on naming convention would have to augmented by assigning the
TestFixtureAttribute to all fixtures and TestAttribute to all tests.
Depending on the number of tests this might a substantial work.

Please sent your feedback and comments to manfred at csunit dot org.
Thank you!

Kind regards,
Manfred.
---
Manfred Lange
co-author csUnit
http://www.csunit. <http://www.csunit.org> org
http://manfredlange <http://manfredlange.blogspot.com> .blogspot.com







[Non-text portions of this message have been removed]

>  For what is worth I think this is a great idea.

Agreed :)


Glenn Crouch mailto:glenn@...
ESB Consultancy http://www.esbconsult.com
Home of ESBPCS & ESB Calculators
Kalgoorlie-Boulder, Western Australia

Manfred,

  For what is worth I think this is a great idea.

Steven Evans



   _____

From: csunit@yahoogroups.com [mailto:csunit@yahoogroups.com] On Behalf Of
manfred_lange_agile
Sent: 23 August 2006 10:50
To: csunit@yahoogroups.com
Subject: [csunit] Proposal: Discontinue support for detecting tests and
fixtures based on naming c



Hi,

we are considering to drop csUnit's support for finding Tests and
TestFixtures based on naming conventions, e.g. fixture names end with
Test and tests starting with Test.

Instead I'd like to change the specification so that it becomes a
requirement to use attributes, e.g. TestFixtureAttribute and
TestAttribute, to mark fixtures and tests.

The benefits would be simplified code with less options for defects.
Also, use of csUnit would be more consistent with
TestAssemblyFixtureAttribute etc.

The impact would be that all test fixtures and all tests that still
rely on naming convention would have to augmented by assigning the
TestFixtureAttribute to all fixtures and TestAttribute to all tests.
Depending on the number of tests this might a substantial work.

Please sent your feedback and comments to manfred at csunit dot org.
Thank you!

Kind regards,
Manfred.
---
Manfred Lange
co-author csUnit
http://www.csunit. <http://www.csunit.org> org
http://manfredlange <http://manfredlange.blogspot.com> .blogspot.com





[Non-text portions of this message have been removed]

Hi,

we are considering to drop csUnit's support for finding Tests and
TestFixtures based on naming conventions, e.g. fixture names end with
Test and tests starting with Test.

Instead I'd like to change the specification so that it becomes a
requirement to use attributes, e.g. TestFixtureAttribute and
TestAttribute, to mark fixtures and tests.

The benefits would be simplified code with less options for defects.
Also, use of csUnit would be more consistent with
TestAssemblyFixtureAttribute etc.

The impact would be that all test fixtures and all tests that still
rely on naming convention would have to augmented by assigning the
TestFixtureAttribute to all fixtures and TestAttribute to all tests.
Depending on the number of tests this might a substantial work.

Please sent your feedback and comments to manfred at csunit dot org.
Thank you!

Kind regards,
Manfred.
---
Manfred Lange
co-author csUnit
http://www.csunit.org
http://manfredlange.blogspot.com

csUnit 2.0.4 Released
=====================
csUnit 2.0.4 has been released and is available for download at
http//www.csunit.org/download.

This release has been tested with .NET 1.1 and VS.NET 2003 including a
side-by-side installation of VS2003 and VS2005.

This is a maintenance release and contains the following bugfixes:

1) BUGFIX, VS2003 wizard: Can't find wizard.config (SourceForge Tracker
ID 1528508)

All bugfixes have been carried over to the 2.1.* head revision as well
so that they are incorporated into the next 2.1 beta version.


.NET 2.0 and VS 2005
====================
A beta version has been made available for .NET 2.0 in March 2006. This
also includes an addin for VS 2005.

It can be downloaded at http://www.csunit.org/download

Please support the project with your donation (see button at
http://www.csunit.org/download). Thank you!


About csUnit
============
Inspired by JUnit, csUnit brings the power of unit testing to the .NET
framework. csUnit is your key to unit testing and test-driven
development using .NET languages such as C#, Visual Basic .NET, Visual
J#, or Managed C++. csUnit was founded in 2001. For more information see
http://www.csunit.org.



Kind regards,
Manfred.
---
Manfred Lange.
csUnit lead developer
Email: manfred_@_csunit_._org (remove underscores)
http://www.csunit.org



[Non-text portions of this message have been removed]

I just got started using csUnit in my visual basic .net project, and
it's great (Visual Studio 2005). Only thing is I can't figure out how
to debug just one test. I can use csUnitRunner, which lets me choose
the test but not debug; or I can use F5 (after setting my test project
as the startup project) and debug all my tests. But if I'm working on
one failing test there isn't an easy way to run just that one, that I see.

Right now I'm using the <ignore> attribute on all the test fixtures
I'm NOT working on, but that's kludgey--I have to go edit a bunch of
test files. Is there a better way?

Hugh

I will give that a try.  Thanks!

Doug

-----Original Message-----
From: csunit@yahoogroups.com [mailto:csunit@yahoogroups.com]On Behalf Of
Andreas Major
Sent: July 12, 2006 5:37 AM
To: csunit@yahoogroups.com
Subject: Re: [csunit] installation problem


Hi,

If you are using Visual Studio .NET 2002 a folder structure in your registry
is missing. The installer of csUnit does only look into
HKEY_LOCAL_MACHINE/Software/Microsoft/Visual Studio/7.1 to find the
installation path. So I created this folder in my registry by myself.

Regards,
    Andreas

-------- Original-Nachricht --------
Datum: Tue, 11 Jul 2006 18:04:47 -0000
Von: d127morgan <dmorgan127@...>
An: csunit@yahoogroups.com
Betreff: [csunit] installation problem

> When attempting to install csunit I get the following error message:
>
> "Could not access the following network location -
> Common7/IDE/PrivateAssemblies"
>
> I have the Express edition of C# installed and have successfully
> created a working example program.
>
> Does anyone have an idea as to what is going wrong?
>
> Thanks.
>
> Doug
>
>
>

--


Echte DSL-Flatrate dauerhaft für 0,- Euro*!
"Feel free" mit GMX DSL! http://www.gmx.net/de/go/dsl


For further information please visit
csUnit's web site at http://www.csunit.org
Yahoo! Groups Links

Hi,

If you are using Visual Studio .NET 2002 a folder structure in your registry is
missing. The installer of csUnit does only look into
HKEY_LOCAL_MACHINE/Software/Microsoft/Visual Studio/7.1 to find the installation
path. So I created this folder in my registry by myself.

Regards,
    Andreas

-------- Original-Nachricht --------
Datum: Tue, 11 Jul 2006 18:04:47 -0000
Von: d127morgan <dmorgan127@...>
An: csunit@yahoogroups.com
Betreff: [csunit] installation problem

> When attempting to install csunit I get the following error message:
>
> "Could not access the following network location -
> Common7/IDE/PrivateAssemblies"
>
> I have the Express edition of C# installed and have successfully
> created a working example program.
>
> Does anyone have an idea as to what is going wrong?
>
> Thanks.
>
> Doug
>
>
>

--


Echte DSL-Flatrate dauerhaft für 0,- Euro*!
"Feel free" mit GMX DSL! http://www.gmx.net/de/go/dsl

When attempting to install csunit I get the following error message:

"Could not access the following network location -
Common7/IDE/PrivateAssemblies"

I have the Express edition of C# installed and have successfully
created a working example program.

Does anyone have an idea as to what is going wrong?

Thanks.

Doug

I forgot to mention:
csUnit 2.1.1-Beta
ReSharper 2.0
Visual Source Safe 2005

   ----- Original Message -----
   From: Elliot Finley
   To: csunit@yahoogroups.com
   Sent: Monday, June 26, 2006 9:40 PM
   Subject: [csunit] side by side install, one works, one doesn't


   Hello,

   I installed the following software on both my desktop and my laptop. I had
   them side by side and followed exactly the same steps:

   VSPro 2005
   csUnit
   ReSharper
   Visual Source Safe.

   I started a solution with 3 projects on my desktop. After building a few
   classes along with their tests, I checked the solution into VSS. I then
   checked the solution out on my laptop which worked fine except that unit
   tests won't work. I can pull up the unit test classes and the unit test
   symbols that should appear in the left column don't appear. The run unit
   tests menu option is greyed out. The 'run all unit tests' option is
   selectable, but it doesn't do anything.

   Any pointers would be appreciated.

   Thanks
   Elliot






------------------------------------------------------------------------------


   No virus found in this incoming message.
   Checked by AVG Free Edition.
   Version: 7.1.394 / Virus Database: 268.9.5/376 - Release Date: 6/26/2006


[Non-text portions of this message have been removed]

Hello,

I installed the following software on both my desktop and my laptop.  I had
them side by side and followed exactly the same steps:

VSPro 2005
csUnit
ReSharper
Visual Source Safe.

I started a solution with 3 projects on my desktop.  After building a few
classes along with their tests,  I checked the solution into VSS.  I then
checked the solution out on my laptop which worked fine except that unit
tests won't work.  I can pull up the unit test classes and the unit test
symbols that should appear in the left column don't appear.  The run unit
tests menu option is greyed out.  The 'run all unit tests' option is
selectable, but it doesn't do anything.

Any pointers would be appreciated.

Thanks
Elliot

Hello,

i have problems to run csUnit 2.1.1 BETA in Visual Studio 2k5 Pro (German). The
problem is, that i can't find any entry in a menu (like shown in screen shots on
www.csUnit.org). But I can find an entry in the Addin manager of VS.
I already tried the advice with "devnev.exe /setup". But as you assume it
doesn't work.
I hope anyone can help me.

Thanks...



[Non-text portions of this message have been removed]

Hello,

I try to install CSUnit version 2.0.3.

The installation fails.

On my computer already installed version csUnit 1.9.4.

Any idea?

 

 

Thank you for help,

Nana Messerer

Hi,

  I am trying to create the test class lib as you suggested but keep getting the following error, in the csUnit output plain.

 

What’s  going wrong

 

System.NullReferenceException: Object reference not set to an instance of an object.

   at csUnit.VSAddIn.MainForm.RefreshRecipe()

   at csUnit.VSAddIn.MainForm.SolutionEvents_Opened()

   at csUnit.VSAddIn.MainForm..ctor(DTE dte)