|
I did try this ages ago but can't remember much about it. J# has a big integer class - see here[^], you can use this from C#.
There is also IntX[^] which I've never used but seen recommended.
|
|
|
|
|
Hi,
I am using VS 2008 to develop an application. In this application
i have List<> of Contacts. This list may contain thousands of contact's.
I have
class Contact
{
......
.........
};
i want to give a signal to all instances of this class that a changed had happen. How can i do this.
thanks
Nitheesh
Jose Jo Martin
http://www.simpletools.co.in
|
|
|
|
|
|
how can i compile file from DOS and make if an exe file?
|
|
|
|
|
|
|
alternative for this:
MemoryStream ms = new MemoryStream();
ms.Write("one exe file");
Process.Start(ms);
)
i have an encoded exe, i want to decode it on memorystream and then run it, so nobody can see original exe file! so i can not use a temp file on HDD!
other way?
modified on Tuesday, September 8, 2009 10:06 AM
|
|
|
|
|
Write it to a temporary file?
|
|
|
|
|
This may sound like a stupid question, but why would you want to do that? If you have the process name, path and parameters why put it to a stream fisrt? If the stream contains more than the name, path and parameters, then what do you expect to happen with the excess data?
No trees were harmed in the sending of this message; however, a significant number of electrons were slightly inconvenienced.
This message is made of fully recyclable Zeros and Ones
|
|
|
|
|
There is no other way. You have to write it to a temporary file. Besides, if your app requires that kind of security, you're still not going to stop the right person from grabbing it straight out of memory.
|
|
|
|
|
you might create a (temporary) memory-resident file system, create a file in there, and execute it. Google + some stamina required.
klik[^]
modified on Tuesday, September 8, 2009 1:04 PM
|
|
|
|
|
Luc Pattyn wrote: you might create a (temporary) memory-resident file system, create a file in there, and execute it. Google + some stamina required.
I was going to suggest writing his own Loader in place of Windows version, but I thought it would have been a bit too overboard.
|
|
|
|
|
Dave Kreskowiak wrote: a bit too overboard.
Nah. If and when we go too overboard, we get a "plz send me the code" reply to straighten us out.
|
|
|
|
|
Hi all
I've made a web service client, that I'm going to use to call a public web service.
But I keep getting this error:
Could not find endpoint element with name 'basicHttpEndpoint' and contract 'oes.dk.NavisionStatIntegrationService.INavisionStatIntegrationService' in the ServiceModel client configuration section. This might be because no configuration file was found for your application, or because no endpoint element matching this name could be found in the client element.
I'm rather new at this web service thing, so I'm not sure what to do here.
I've been browsing the net for answers but nothing good has come up.
This is the client part of the app.config:
<client><br />
<endpoint address="https://test3.oes.dk/NavisionStatIntegrationServiceTest/NavisionStatIntegrationService.svc"<br />
binding="basicHttpBinding" bindingConfiguration="basicHttpEndpointBinding"<br />
contract="oes.dk.NavisionStatIntegrationService.INavisionStatIntegrationService"<br />
name="basicHttpEndpoint" /><br />
</client>
The code I call:
proxy = new NavisionStatIntegrationServiceClient("basicHttpEndpoint");<br />
proxy.ClientCredentials.UserName.UserName = this.UserName;<br />
proxy.ClientCredentials.UserName.Password = this.Password;<br />
this.NSResponse = proxy.InvokeNavisionStatIntegration(this.companyIdentifier, this.immediateExecuting, this.NSRequest);<br />
return this.NSResponse;
This is the code for the NavisionStatIntegrationServiceClient:
[System.CodeDom.Compiler.GeneratedCodeAttribute("System.ServiceModel", "3.0.0.0")]<br />
[System.ServiceModel.ServiceContractAttribute(Namespace = "http://www.oes.dk/NavisionStatIntegrationService/2009/05/25", ConfigurationName = "oes.dk.NavisionStatIntegrationService.INavisionStatIntegrationService")]<br />
public interface INavisionStatIntegrationService<br />
{<br />
[System.ServiceModel.OperationContractAttribute(Action = "http://www.oes.dk/NavisionStatIntegrationService/2009/05/25/INavisionStatIntegrat" +<br />
"ionService/InvokeNavisionStatIntegration", ReplyAction = "http://www.oes.dk/NavisionStatIntegrationService/2009/05/25/INavisionStatIntegrat" +<br />
"ionService/InvokeNavisionStatIntegrationResponse")]<br />
string InvokeNavisionStatIntegration(string companyIdentifier, string immediateExecuting, string NSRequest);<br />
}
|
|
|
|
|
You'll get a much better response if you post this in the WPF/ WCF / WF forum instead.
|
|
|
|
|
|
Please verify that the .config file is copied together with the exe. The config has the same name as the exe, e.g. MyApp.exe.config. Check if this file has the client-element within.
If the file is missing, right-click on App.config in the Project Explorer ro open the properties and select "Copy always".
Regards
Sebastian
|
|
|
|
|
The .config file is copied together with the .dll and has the same name, Application.dll and Application.dll.config.
The config has the client element from my original posting.
Best regards
Soren
|
|
|
|
|
Well, that is not really how it is working. If you are using the dll within an application, you have to put the client-definition in the config-file for the application.
|
|
|
|
|
I didn't know that but tried it out.
It worked like a charm.
Thx for the input.
|
|
|
|
|
The solution was to put the system.serviceModel part of my .config into application.exe.config.
My original .config was application.dll.config.
This was done, because my .dll was to be called from a foreign program, and I didn't know that the configuration had to be done in that program.
Thx for the input.
|
|
|
|
|
how can i convert an int number to hex?
|
|
|
|
|
someInteger.ToString("X8")
|
|
|
|
|
Cool - I've never spotted "X8".
I've always used the Convert class
Convert.ToString(intValue, base)
|
|
|
|
|
unfortunately there is no similar code for octal or binary, things people around here seem to want often.
|
|
|
|