I'm posting this in case others hit the same issue.
When trying to doa ClickOnce deployment, we hit the following error:
"Cannot publish because a project failed to build."
"SignTool reported an error. "The parameter is incorrect."
We switched from VB to C# and it worked fine. I'll leave this blog posting out on the net so it can help someone else out doing ClickOnce deployments.
This blog is designed to show various ways to use Data Virtualization, technologies, and SAS with Microsoft technologies with an eye toward outside of the box thinking.
Thursday, August 31, 2006
Sunday, August 06, 2006
EG Tasks not displaying
Installed EG4.1 and no task were displayed. Here's how I fixed it (based upon an old 2.0 TS post):
Go to:
Tools > SAS Enterprise Guide Explorer >
In Enterprise Guide Explorer
Tools > Options > Uncheck Enable Task Administration
Go to:
Tools > SAS Enterprise Guide Explorer >
In Enterprise Guide Explorer
Tools > Options > Uncheck Enable Task Administration
SAS EG and .NET 2.0
Ok, so the official word is no .NET 2.0 apps in EG. I understand this position 100% and I agree with the position. Regardless, .NET 2.0 costs me 25-50% less effort than 1.1 so my goal was to see if I could hack out something that would allow me to post a 2.0 app in EG 4.1.
It is a hack, it's not official, it's limited, etc. but I successfully got my 2.0 app to run under EG and had it post my code to an EG task. Here's how I did it but it is simplistic and not pretty. I share it in case you need something similar.
First, create a 2.0 app. Make it a WinForm and have fun on layout, generics, etc.
Then change parts of your program.cs to something like the following:
MainForm frm = new MainForm();
Application.Run(frm);
Console.WriteLine(frm.SasCode);
All Winform apps can write to a console but this output goes to a standard out.
Then change your EG add-in to support it:
public SAS.Shared.AddIns.ShowResult Show(System.Windows.Forms.IWin32Window Owner)
{
Process proc ;
proc = new Process() ;
proc.StartInfo.UseShellExecute = false ;
proc.StartInfo.RedirectStandardOutput = true ;
proc.StartInfo.RedirectStandardError = true ;
proc.StartInfo.CreateNoWindow = true ;
proc.StartInfo.FileName = "AnalystToolkit.exe";
proc.Start() ;
proc.WaitForExit() ;
sasCode = proc.StandardOutput.ReadToEnd() ;
return SAS.Shared.AddIns.ShowResult.RunLater;
}
I could have done a lot more with standard out (and I probably will) but this shows you a quick and easy way to hack up a solution that works. From this standard out, you should be able to make out a way to do anything you need.
From out in left field and having fun,
Alan
It is a hack, it's not official, it's limited, etc. but I successfully got my 2.0 app to run under EG and had it post my code to an EG task. Here's how I did it but it is simplistic and not pretty. I share it in case you need something similar.
First, create a 2.0 app. Make it a WinForm and have fun on layout, generics, etc.
Then change parts of your program.cs to something like the following:
MainForm frm = new MainForm();
Application.Run(frm);
Console.WriteLine(frm.SasCode);
All Winform apps can write to a console but this output goes to a standard out.
Then change your EG add-in to support it:
public SAS.Shared.AddIns.ShowResult Show(System.Windows.Forms.IWin32Window Owner)
{
Process proc ;
proc = new Process() ;
proc.StartInfo.UseShellExecute = false ;
proc.StartInfo.RedirectStandardOutput = true ;
proc.StartInfo.RedirectStandardError = true ;
proc.StartInfo.CreateNoWindow = true ;
proc.StartInfo.FileName = "AnalystToolkit.exe";
proc.Start() ;
proc.WaitForExit() ;
sasCode = proc.StandardOutput.ReadToEnd() ;
return SAS.Shared.AddIns.ShowResult.RunLater;
}
I could have done a lot more with standard out (and I probably will) but this shows you a quick and easy way to hack up a solution that works. From this standard out, you should be able to make out a way to do anything you need.
From out in left field and having fun,
Alan
Subscribe to:
Posts (Atom)
SAS throwing RPC error
If you are doing code in C# and get this error when creating a LanguageService: The RPC server is unavailable. (Exception from HRESULT:...
-
I was just tasked to read in LDAP records so we could cross-reference userids with login identifiers and general ledger information. Using...
-
I am finally ready with my SAS dataset reader/writer for .NET. It is written in 100% managed code using .NET 3.5. The dlls can be found here...
-
Well, around 14 months ago, I started on a journey to understand the SAS dataset so I could read and write one independently. Originally, I ...