
Testing a method in vsinterdev through console window?
Thanks for your answer Jan :)
Seems vs.net does not have the same capabilities as VB6 had - i guess i'll
have to live with that when i think of all the other benefits i'm getting :)
And i know i have to instanciate my objects to use them - unless i made a
static method? - i used (in vb6) to be able to do this in the immediate
window:
set q = new myobject
?q.mymethod(somevariable)
That was a cool feature, making it possible to test/debug/trace a newly made
method in the project i was working on. I hope to see this feature
implemented in a future version of visual studio - i understand i'd have to
build first and all, but it should be possible, if the immediate window had
some extra functionality - like a small "project" with a default using of
the namespace(s) your project was using or something like that - should be
possible, but i know there are lots of stuff that could be implemented, i
just think this would be my top priority :)
Per
Quote:
> hi per,
> you can create an additional console or library project in your solution,
> import the other project to the newly created one and
> write a test suite there. you might also think about the blessings of unit
> testing --> www.nunit.org
> but of course you cannot test a method without instanteating the oject
that
> contains it. that's what oo is all about...
> jan
> ----- Original Message -----
> Newsgroups:
microsoft.public.dotnet.framework,microsoft.public.vsnet.general,microsoft.
p
Quote:
> ublic.dotnet.languages.csharp
> Sent: Thursday, October 10, 2002 08:05
> Subject: Testing a method in vsinterdev through console window?
> > Hey everybody :)
> > I've been working with c# and visual interdev for some time now and i
> can't
> > seem to find an easy way to test, say a new method i created for an
> asp.net
> > application. Before .NET i was using VB to build COM objects and i had t
he
> > little debug window where i could instanciate classes etc. and then
> calling
> > methods, while tracing/debugging - now i seem to get a lot of "can't
> > evaluate expression" - is the only way for me to test a method now, to
> make
> > the application call it and then trace?
> > How do you guys do it?
> > Thanks in advance :)