Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Since you did not show the actual page name in your posted code, I am going to assume that <code>tesing.aspx</code> is supposed to be <code>testing.aspx</code>, change your URL to this:</p> <pre><code>/testing/testing.aspx </code></pre> <p>UPDATE 1:</p> <p>You are trying to use in-line embedded code blocks via the <code>&lt;%</code> syntax, but you need to use the <code>&lt;script</code> syntax because your logic is spanning more than a single line.</p> <p>Try this instead:</p> <pre><code>&lt;script runat="server"&gt; using System; protected string callRotate() ... Rest of your code here &lt;/script&gt; </code></pre> <p>UPDATE 2:</p> <p>Embedded code blocks do not allow for the use of the C# <code>using</code> statement, instead you have to use the <code>@ Import</code> page directive, like this:</p> <pre><code>&lt;%@ Import Namespace="System" %&gt; </code></pre> <p>UPDATE 3:</p> <p>The <code>ProcessStartInfo</code> class is part of the <code>System.Diagnostics</code> namespace, so add the following import for that, like this:</p> <pre><code>&lt;%@ Import Namespace="System.Diagnostics" %&gt; </code></pre> <p>UPDATE 4:</p> <p>You can combine your file name and arguments together, like this:</p> <pre><code>Process execute = new Process(); execute.StartInfo.FileName = "ConsoleApplication1"; execute.StartInfo.Arguments = @"-log d:file.txt -c ""arg2"" -y ""arg3"" -z ""HOW?"""; execute.Start() </code></pre> <p>Note: The <code>Arguments</code> value here is made up, because I am not sure what flags you have setup in your console application named <code>ConsoleApplication1</code>.</p> <p>UPDATE 5:</p> <p>Change the method in your <code>script</code> block to handle the ASP.NET Page_Load event, like this:</p> <pre><code>protected void Page_Load(object sender, EventArgs e) { string url = Request.QueryString["url"]; string rotate_dir = Request.QueryString["dir"]; } </code></pre>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload