wfSpy and VS2005
by SQACSharp on 11/1/2007 5:28:00 AM
I download wfspy src from http://www.codeproject.com/dotnet/wfspy.asp
and convert and compile the source in VS 2005
I can generate the .exe and .dll but the compiler return the error :
"Error spawning 'cmd.exe'
Since the error is not stopping the generation of the .exe and .dll I
have modified the code to show .Net 2.0 window also. Cool!! now I
can
have both .net 1.0 and 2.0 window listed in the treeview but it's not
working as expected
Questions
=========
1- What is that Error spawning CMD.EXE ??? How to fix this ???
2- Now I can list 1.0 and 2.0 window in the same treeview (the list
of
window) but i can only get the properties for 2.0 window/
controls ????
Why??? Just because I load the source in VS2005 instead of VS2003
like the author I get an exception for 1.0 controls and 2.0 control
are now working??? This make no sense? The demo .exe/.dll posted in
codeproject do the opposite...it correctly list properties of 1.0
controls??? Is it suppose to be like this????
If I can fix the cmd.exe error maybe I will be able to debug to
understand why it fail.
Thanks
Re: wfSpy and VS2005
by Nicholas Paldino [.NET/C# MVP] on 11/1/2007 11:41:00 AM
You are more than likely going to get a response from the person that
wrote that utility. It's not a standard MS utility, nor, AFAIK, a very
popular one (I haven't heard of it until now), so your best bet is with the
original author.
--
- Nicholas Paldino [.NET/C# MVP]
- mvp@spam.guard.caspershouse.com
"SQACSharp" <lsdisciples@hotmail.com> wrote in message
news:1193945268.424513.112020@v3g2000hsg.googlegroups.com...
>I download wfspy src from http://www.codeproject.com/dotnet/wfspy.asp
> and convert and compile the source in VS 2005
>
> I can generate the .exe and .dll but the compiler return the error :
> "Error spawning 'cmd.exe'
>
> Since the error is not stopping the generation of the .exe and .dll I
> have modified the code to show .Net 2.0 window also. Cool!! now I
> can
> have both .net 1.0 and 2.0 window listed in the treeview but it's not
> working as expected
>
>
> Questions
> =========
> 1- What is that Error spawning CMD.EXE ??? How to fix this ???
> 2- Now I can list 1.0 and 2.0 window in the same treeview (the list
> of
> window) but i can only get the properties for 2.0 window/
> controls ????
> Why??? Just because I load the source in VS2005 instead of VS2003
> like the author I get an exception for 1.0 controls and 2.0 control
> are now working??? This make no sense? The demo .exe/.dll posted in
> codeproject do the opposite...it correctly list properties of 1.0
> controls??? Is it suppose to be like this????
>
>
> If I can fix the cmd.exe error maybe I will be able to debug to
> understand why it fail.
>
> Thanks
>
Re: wfSpy and VS2005
by SQACSharp on 11/1/2007 6:09:00 AM
On Nov 1, 3:41 pm, "Nicholas Paldino [.NET/C# MVP]"
<m...@spam.guard.caspershouse.com> wrote:
> You are more than likely going to get a response from the person that
> wrote that utility. It's not a standard MS utility, nor, AFAIK, a very
> popular one (I haven't heard of it until now), so your best bet is with the
> original author.
>
> --
> - Nicholas Paldino [.NET/C# MVP]
> - m...@spam.guard.caspershouse.com
>
> "SQACSharp" <lsdiscip...@hotmail.com> wrote in message
>
> news:1193945268.424513.112020@v3g2000hsg.googlegroups.com...
>
>
>
> >I download wfspy src fromhttp://www.codeproject.com/dotnet/wfspy.asp
> > and convert and compile the source in VS 2005
>
> > I can generate the .exe and .dll but the compiler return the error :
> > "Error spawning 'cmd.exe'
>
> > Since the error is not stopping the generation of the .exe and .dll I
> > have modified the code to show .Net 2.0 window also. Cool!! now I
> > can
> > have both .net 1.0 and 2.0 window listed in the treeview but it's not
> > working as expected
>
> > Questions
> > =========
> > 1- What is that Error spawning CMD.EXE ??? How to fix this ???
> > 2- Now I can list 1.0 and 2.0 window in the same treeview (the list
> > of
> > window) but i can only get the properties for 2.0 window/
> > controls ????
> > Why??? Just because I load the source in VS2005 instead of VS2003
> > like the author I get an exception for 1.0 controls and 2.0 control
> > are now working??? This make no sense? The demo .exe/.dll posted in
> > codeproject do the opposite...it correctly list properties of 1.0
> > controls??? Is it suppose to be like this????
>
> > If I can fix the cmd.exe error maybe I will be able to debug to
> > understand why it fail.
>
> > Thanks- Hide quoted text -
>
> - Show quoted text -
I get no answer from the author... but my question is not releated to
the tool :
My question was more about the error "Error spawning CMD.EXE" ....the
compiler give no infos at all... just this error...
Re: wfSpy and VS2005
by Andy on 11/1/2007 6:24:00 AM
On Nov 1, 4:08 pm, SQACSharp <lsdiscip...@hotmail.com> wrote:
> On Nov 1, 3:41 pm, "Nicholas Paldino [.NET/C# MVP]"
>
>
>
>
>
> <m...@spam.guard.caspershouse.com> wrote:
> > You are more than likely going to get a response from the person that
> > wrote that utility. It's not a standard MS utility, nor, AFAIK, a very
> > popular one (I haven't heard of it until now), so your best bet is with the
> > original author.
>
> > --
> > - Nicholas Paldino [.NET/C# MVP]
> > - m...@spam.guard.caspershouse.com
>
> > "SQACSharp" <lsdiscip...@hotmail.com> wrote in message
>
> >news:1193945268.424513.112020@v3g2000hsg.googlegroups.com...
>
> > >I download wfspy src fromhttp://www.codeproject.com/dotnet/wfspy.asp
> > > and convert and compile the source in VS 2005
>
> > > I can generate the .exe and .dll but the compiler return the error :
> > > "Error spawning 'cmd.exe'
>
> > > Since the error is not stopping the generation of the .exe and .dll I
> > > have modified the code to show .Net 2.0 window also. Cool!! now I
> > > can
> > > have both .net 1.0 and 2.0 window listed in the treeview but it's not
> > > working as expected
>
> > > Questions
> > > =========
> > > 1- What is that Error spawning CMD.EXE ??? How to fix this ???
> > > 2- Now I can list 1.0 and 2.0 window in the same treeview (the list
> > > of
> > > window) but i can only get the properties for 2.0 window/
> > > controls ????
> > > Why??? Just because I load the source in VS2005 instead of VS2003
> > > like the author I get an exception for 1.0 controls and 2.0 control
> > > are now working??? This make no sense? The demo .exe/.dll posted in
> > > codeproject do the opposite...it correctly list properties of 1.0
> > > controls??? Is it suppose to be like this????
>
> > > If I can fix the cmd.exe error maybe I will be able to debug to
> > > understand why it fail.
>
> > > Thanks- Hide quoted text -
>
> > - Show quoted text -
>
> I get no answer from the author... but my question is not releated to
> the tool :
>
> My question was more about the error "Error spawning CMD.EXE" ....the
> compiler give no infos at all... just this error...- Hide quoted text -
>
> - Show quoted text -
Did you check the project build events tab? its probably something in
there if you get this whenver you compile
Re: wfSpy and VS2005
by SQACSharp on 11/1/2007 6:35:00 AM
On Nov 1, 4:24 pm, Andy <an...@med-associates.com> wrote:
> On Nov 1, 4:08 pm, SQACSharp <lsdiscip...@hotmail.com> wrote:
>
>
>
>
>
> > On Nov 1, 3:41 pm, "Nicholas Paldino [.NET/C# MVP]"
>
> > <m...@spam.guard.caspershouse.com> wrote:
> > > You are more than likely going to get a response from the person that
> > > wrote that utility. It's not a standard MS utility, nor, AFAIK, a very
> > > popular one (I haven't heard of it until now), so your best bet is with the
> > > original author.
>
> > > --
> > > - Nicholas Paldino [.NET/C# MVP]
> > > - m...@spam.guard.caspershouse.com
>
> > > "SQACSharp" <lsdiscip...@hotmail.com> wrote in message
>
> > >news:1193945268.424513.112020@v3g2000hsg.googlegroups.com...
>
> > > >I download wfspy src fromhttp://www.codeproject.com/dotnet/wfspy.asp
> > > > and convert and compile the source in VS 2005
>
> > > > I can generate the .exe and .dll but the compiler return the error :
> > > > "Error spawning 'cmd.exe'
>
> > > > Since the error is not stopping the generation of the .exe and .dll I
> > > > have modified the code to show .Net 2.0 window also. Cool!! now I
> > > > can
> > > > have both .net 1.0 and 2.0 window listed in the treeview but it's not
> > > > working as expected
>
> > > > Questions
> > > > =========
> > > > 1- What is that Error spawning CMD.EXE ??? How to fix this ???
> > > > 2- Now I can list 1.0 and 2.0 window in the same treeview (the list
> > > > of
> > > > window) but i can only get the properties for 2.0 window/
> > > > controls ????
> > > > Why??? Just because I load the source in VS2005 instead of VS2003
> > > > like the author I get an exception for 1.0 controls and 2.0 control
> > > > are now working??? This make no sense? The demo .exe/.dll posted in
> > > > codeproject do the opposite...it correctly list properties of 1.0
> > > > controls??? Is it suppose to be like this????
>
> > > > If I can fix the cmd.exe error maybe I will be able to debug to
> > > > understand why it fail.
>
> > > > Thanks- Hide quoted text -
>
> > > - Show quoted text -
>
> > I get no answer from the author... but my question is not releated to
> > the tool :
>
> > My question was more about the error "Error spawning CMD.EXE" ....the
> > compiler give no infos at all... just this error...- Hide quoted text -
>
> > - Show quoted text -
>
> Did you check the project build events tab? its probably something in
> there if you get this whenver you compile- Hide quoted text -
>
> - Show quoted text -
There is nothing in that tab...no commandline or specific config...
Re: wfSpy and VS2005
by SQACSharp on 11/4/2007 5:43:00 AM
Is upgrading a .net 1.1 application (done in VS 2003) in VS 2005 is
also upgrading the application to .net 2.0 framework???? Thanks!
Re: wfSpy and VS2005
by SQACSharp on 11/4/2007 2:51:00 PM
On 4 nov, 16:43, SQACSharp <lsdiscip...@hotmail.com> wrote:
> Is upgrading a .net 1.1 application (done in VS 2003) in VS 2005 is
> also upgrading the application to .net 2.0 framework???? Thanks!
After loosing hours on this....
The answer is yes... :(
Now trying to figure out how to create a .net 1.x version of my
2.0 .net application.