Run external app
-
Using .Net 2.0... I'm using System.Diagnostics, but there is not "Process" item according to intellisense. Did MS move it to another assembly?
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001John Simmons / outlaw programmer wrote:
Did MS move it to another assembly?
No, they didn't. Either add using System.Diagnostics; to the usings and then you will have access to Process class in your source code file or just write the full name when you need to access process class System.Diagnostics.Process pr=new System.Diagnostics.Process();
#region signature my articles #endregion
-
John Simmons / outlaw programmer wrote:
Did MS move it to another assembly?
No, they didn't. Either add using System.Diagnostics; to the usings and then you will have access to Process class in your source code file or just write the full name when you need to access process class System.Diagnostics.Process pr=new System.Diagnostics.Process();
#region signature my articles #endregion
I've tried it both ways. I even went ot see if I needed to add a reference to system.diagnostics, and the assembly isn't referenceable that way. So, now what?
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001 -
I've tried it both ways. I even went ot see if I needed to add a reference to system.diagnostics, and the assembly isn't referenceable that way. So, now what?
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001 -
led mike wrote:
Something must be broken because it's there.
Saying that a Microsoft product is broken is like looking at a flat tire and saying there's no air in it. :)
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001 -
Could it be that I can't run an external app from a web app?
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001 -
Could it be that I can't run an external app from a web app?
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001You can, but it will run on the server and that's probably not what you're trying to achieve.
Deja View - the feeling that you've seen this post before.
-
I've tried it both ways. I even went ot see if I needed to add a reference to system.diagnostics, and the assembly isn't referenceable that way. So, now what?
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001Intellisense doesn't always work as expected. Try the following: 1. Recompile your code (this may work, but most likely not). 2. Close the tab (file) and reopen it. This should cause intellisense to look at the file again. 3. Restart the IDE. Beyound those three, you will have to delete all intermediate files including *.suo files. Then it should work again. The problem that I see here is that intellisense is not working as expected.
Phil
-
Could it be that I can't run an external app from a web app?
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001 -
Using .Net 2.0... I'm using System.Diagnostics, but there is not "Process" item according to intellisense. Did MS move it to another assembly?
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001This whole thing started out as a conversion from PHP to C#. I started out by adding a new class to an existing web site project at home (because it seemed to be the right thing to do). I then emailed it to myself at work, and added the class to a winforms app. Well, it still had all the using web*.* lines in it, so I got to thinkin... I created a new web site and added this class to the site, and bingo! Intellisense is showing me what I want/expect.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001 -
This whole thing started out as a conversion from PHP to C#. I started out by adding a new class to an existing web site project at home (because it seemed to be the right thing to do). I then emailed it to myself at work, and added the class to a winforms app. Well, it still had all the using web*.* lines in it, so I got to thinkin... I created a new web site and added this class to the site, and bingo! Intellisense is showing me what I want/expect.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001I bet you didn't have a reference to System.dll in your older projects while your new projetcs automatically got it. Robert
-
I bet you didn't have a reference to System.dll in your older projects while your new projetcs automatically got it. Robert
Well, you're wrong. All classes created in VS2005 with the templates automatically have
using System;in the cs file."Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001 -
Well, you're wrong. All classes created in VS2005 with the templates automatically have
using System;in the cs file."Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001I didn't mean the
using System. What I mean is the reference to theSystem.dllof your project. It might have not been added in the conversion. Removing it from the references of a newly created project reproduces your described behaviour: TheSystem.Diagnosticsnamespace is there... but noProcessclass. Robert
