|
I need to do the same thing...did you ever figure it out?
Gary Kirkham
A working Program is one that has only unobserved bugs
I thought I wanted a career, turns out I just wanted paychecks
|
|
|
|
|
I want to load and unload a dll-file as an assembly dynamically.
how can I realize it? I only know that I have to use AppDomain, but I don't know how. So can anybody help me?
The content of the dll is a windows form. I used the following code before, but it isn't able to unload:
<br />
Assembly SimpAsm = Assembly.LoadFrom(strFile);<br />
frmTemp = (Form)SimpAsm.CreateInstance(strForm );<br />
frmTemp.Show();<br />
try to help me, please! thanks....
|
|
|
|
|
|
yes there's written many information, but not the real code, which I need.
has anybody an example of using AppDomain? 
|
|
|
|
|
Anyone tried it ? is it worth the extra money going from proffessional ?
Space reserved for wit , humour and correct spelling.
|
|
|
|
|
I made my custom control.When I use it ,very SELDOM my controls are missing form my form.I can not understand the reason.
|
|
|
|
|
Hi!
I have a very odd problem. In the code segment below (from my webapplication) the bool protected variable bNyPost is set to true in Page_Load but when I click Save the variable is false in the procedure SaveUhItem(). Isn't bNyPost global to all the procedures in the class FelRegMobileForm?
namespace DeDUWebMobile
{
public class FelRegMobileForm : System.Web.UI.MobileControls.MobilePage
{
protected bool bNyPost;
private void Page_Load(object sender, System.EventArgs e)
{
if (!IsPostBack)
{
.
.
.
bNyPost = true;
}
}
.
.
private void CDSave_Click(object sender, System.EventArgs e)
{
SaveUhItem();
bNyPost = false;
}
.
.
private void SaveUhItem()
{
if( bNyPost ) //Is false even though I assigned true in Page_Load
{
.
.
}
}
}
}
MSc Bertil Morefält
|
|
|
|
|
Let me try to explain. Each time a client makes a request to the server a new Page object is instantiated and the Load event is executed. If it's the clients first request for the page the IsPostBack property should be false, but if a control is manipulated (ie. a button is clicked) or if there is some other event that causes the client to post back to the server then the IsPostBack property will be true.
So in your situation the bNyPost variable is getting set to true because it is inside the conditional statement.
Brian
|
|
|
|
|
That's right, but when bNyPost is set to true the first time when IsPostBack is false, it should stay true when tested in SaveUhItem() when I click Save-button as the next action, but it don't.
Bertil
MSc Bertil Morefält
|
|
|
|
|
No, a new Page object is created for each request. Thus, those members of the object that are not placed in the viewstate will not maintain their state. You'll have to place that variable in the viewstate manually or use some other form state management.
Brian
|
|
|
|
|
i try to write a little setup, which supports 3 install options (checkbox).
I would like to know the states of my checkboxes, but it seems like i can't
write something like this
((CHECKBOXA1 And CHECKBOXA2) And Not (CHECKBOXA3))
Option 1 checked, Option 2 checked, Option3 unchecked
Does anybody know how to write something above the right way? It seems like
CHECKBOXA3 has no value (null) if it is not checked. Is there any null
keyword for installer conditions?
.:[Greetz from Jerry Maguire]:.
|
|
|
|
|
the syntax of using checkbox is:
checkbox.checked = [true / false];
and then you can control it with "&&"...
|
|
|
|
|
Hallo ich_bins,
i guess you mean the System.Windows.Forms.CheckBox, right ?
what i'm looking for is how to use installer conditions to fire custom actions in a msi setup project.
Thanks for your answer
.:[Greetz from Jerry Maguire]:.
|
|
|
|
|
In my application, I want the user to be able to customize the path to some files.
So I use a OpenFileDialog, and get the path of the new file, and I can open the file.
I'd like to store the path for the next use of the program, but I want to store it relatively to my executable.
But the OpenFileDialog return the absolute path.
So if I have:
e:\Programs\MyProgram\Bin\MyExecutable.exe
and the user select
e:\Programs\MyPrograms\Graphics\MyFile.gif
How can I easily find that the path to store is
..\Graphics\MyFile.gif?
|
|
|
|
|
In shlwapi.dll there is a method called PathRelativePathTo.
α.γεεκ Fortune passes everywhere.
Duke Leto Atreides
|
|
|
|
|
Hello,
Is the format used by BinaryWriter and BinaryReader portable for standard data types like string and uint?
For example, suppose that one uses a BinaryWriter on a machine of type X to write to a NetworkStream, and the other end of the stream is running on a machine of type Y and uses BinaryReader to read from the NetworkStream. Suppose also that both machines are using programs written in C# and being executed by .NET. Will the reader get what was written, regardless of whether X and Y are different types of machines (possibly having different endianness)?
(The BinaryWriter constructor allows one to specify an encoding. I would like to know whether the default encoding is portable in the way described above, and whether the other standard encodings are portable in this way.)
|
|
|
|
|
In answer to your primary question, BinaryReader will read streams created by BinaryWriter correctly.
Your question about endianness is meaningless at the present time because .NET only runs on Intel CPUs and hence you don't have to worry about it. Once Microsoft target .NET for other CPUs then, yes, the .NET Frameowrk team will have to worry about how the stream is created and used between different endian CPUs.
Cheers, Julian
Program Manager, C#
This posting is provided "AS IS" with no warranties, and confers no rights.
|
|
|
|
|
Julian,
Is there complete BinaryWriter/BinaryReader compatibility for all Microsoft .NET implementations and for all pairs of machines that Microsoft's .NET runs on? I tried to be explicit about this in the original post -- if the question is still not clear then I will try to make it clearer. I am looking for an explicitly-written answer that's more informative than, "Some BinaryReader objects can read what's written by some BinaryWriter objects."
The endianness question is meaningful at present because there are different vendors, e.g., Microsoft and Mono, but even information only about Microsoft-to-Microsoft communication would be helpful.
Also, it helps and is even necessary to have some idea of future capabilities. I do not want to release software only to find out in 3 months that a large class of users cannot connect to a server because BinaryWriter and BinaryReader are incompatible in some circumstances, e.g., .NET 2.0 (say) is using a format that is incompatible with .NET 1.0. In fact if this were to happen, then using BinaryWriter/BinaryReader would be painful for many client/server situations because there would be two different classes of users, e.g., many Windows XP users with .NET 1.0 and some other users who are using .NET 2.0. It would become necessary to somehow know in advance which version of the protocol to use, and to be able to use either version within a single assembly (the server).
Andrew
|
|
|
|
|
Andrew
I'm sorry, I see I wasn't being explicit enough <g>. Any stream written with any existing BinaryWriter can be read by any existing BinaryReader. I can even confirm that fact with Whidbey's BinaryReader and Writer (that is, with .NET Framework 2.0). If it didn't then it's a bug. (So the 3D matrix of 1.0, 1.1, 2.0 frameworks, for the two layers of writers and reader combinations has ticks in every cell).
That's the statement about Microsoft's .NET Framework. I know nothing about the Mono project (apart from what it is, of course). I have no idea whether their BinaryReader would always work with a stream createed with BinaryWriter. Similarly I don't know if a stream written by Mono's BinaryWriter would be readable with MS's BinaryReader. However, I would *guess* that the Mono people would have taken endianness into account when they were writing their reader and writer.
Now, as to the future (beyond Whidbey): it would make sense for the .NET Framework team to make sure that BinaryReader and BinaryWriter can continue to work as before. Why? Because the ResourceManager uses BinaryReaders and Writers internally. And that would be bad if Visual Studio .NET X (for X>2) couldn't read resource files from existing projects.
Also, the format used by BinaryWriter is very, very simple and easily reverse engineered. There's no wierdo enums or class names being put in there or stuff like that. An int is written out as 4 bytes, a double as 8, etc, etc.
So, although neither I nor anyone else can really tell you what would happen five years down the road, I wouldn't worry about it.
Cheers, Julian
Program Manager, C#
This posting is provided "AS IS" with no warranties, and confers no rights.
|
|
|
|
|
Thanks Julian. That is just what I wanted to know.
Andrew
|
|
|
|
|
Note also that the version of the assembly must be identical on both ends.
|
|
|
|
|
Arun Bhalla wrote:
Note also that the version of the assembly must be identical on both ends.
Do you mean that the version of .NET that the assembly is using on both sides must be identical? Or do you mean that the version of the assemblies itself must be identical? If the latter this makes no sense because the assembly using BinaryWriter might be different from the assembly using the BinaryReader, e.g., there is a client/server relationship.
|
|
|
|
|
Ooops, sorry I was thinking of BinaryFormatter & Serialization.
|
|
|
|
|
|
what do you think from the following books you most recommend for C# newbie?
Programming C# 3rd Edition by O'REILLY
C# and The .NET Platform, Second Edition
Wrox: Professional C# 2nd Edition
Sybex, Mastering Visual C#.net
MS press c#.net core reference
thnks, i just want to hear your opinion before buying!
nevhile.net
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
