|
I assume it's the File.Copy line that throws the error?
Out of interest, you've not got the picture your copying open in another application have you?
KP
|
|
|
|
|
i known the error is File.Copy line but i cannot find out the to correct it.
please help me again
thanks
Rock Throught The Night
|
|
|
|
|
I have just tried the code with some adjustments for my file structure and it works fine. The only difference between my code and yours is the newpath string, i set mine to @"c:\golfball2.bmp" and when i clicked the update button i got a copy of golfball.bmp called golfball2.bmp.
I assume the problem is that the destination for your file is currently being used by another application, or even by your application. Try hard coding the newPath string to @"c:\test.jpg". If that works then you will have to look at where your trying to write the copy to.
Let me know how you get on.
KP
|
|
|
|
|
the " currentPath " and the newPath is the same Folder and the " currentFileName " and "newFileName" is the same too
so the error occur.
Rock Throught The Night
|
|
|
|
|
Either clone (via Clone - don't forget to cast it to an Image) the Image you get from Image.FromFile, or use a FileStream and specify FileShare.Read at the very least, then read the image from the stream (the Bitmap class - a derivative of Image - accepts a Stream as a parameter).
Microsoft MVP, Visual C#
My Articles
|
|
|
|
|
Hi ppl.
What sort of naming standards should you use for C#?
Should variable names in the class start with "m_str" for example?
thanks
|
|
|
|
|
This is what microsoft dictates...
Naming Guidelines[^]
I think your sopposed to use pascal case for variables and no little prefix....
/\ |_ E X E GG
|
|
|
|
|
eggie5 wrote:
This is what microsoft dictates
Well, Microsoft don't really dictate it, they are called "guidelines" because you can ignore them if you wish. But, obviously if everyone follows the guidelines it becomes easier to maintain and read the code.
"You can have everything in life you want if you will just help enough other people get what they want." --Zig Ziglar
The Second EuroCPian Event will be in Brussels on the 4th of September
Can't manage to P/Invoke that Win32 API in .NET? Why not do interop the wiki way!
My Blog
|
|
|
|
|
Like on Pirates of the Caribbean?
/\ |_ E X E GG
|
|
|
|
|
 Kind of... 
"You can have everything in life you want if you will just help enough other people get what they want." --Zig Ziglar
The Second EuroCPian Event will be in Brussels on the 4th of September
Can't manage to P/Invoke that Win32 API in .NET? Why not do interop the wiki way!
My Blog
|
|
|
|
|
I notice there is no more use of the prefix for the type of the variable anymore. I'm use to using a variable named say "strName" to say the type is a string. Wouldn't the use of just "Name" be a little confusing if you didn't know its type just by looking naming standard for all you know it could be a integer, boolean (hopefully not!)?
|
|
|
|
|
If you are using visual studio or any other ide, you can tell my just leaving your mouse over the variable and it will give you all that info...
/\ |_ E X E GG
|
|
|
|
|
no more notepad then 
|
|
|
|
|
Take also a look at this site[^] from MSDN.
It should give you a general overview before studying the previous posted link.
www.troschuetz.de
|
|
|
|
|
|
Are you gonna extend this into a full-blown managed web browser?
Q:What does the derived class in C# tell to it's parent?
A:All your base are belong to us!
|
|
|
|
|
Currently this only renders xhtml so it would be a quite limited market 
however i am trying to make it as flexible as possible , so if i can find some sparetime
, ill try to add a standard html parser to.
i will only add features to the renderer itself , i will not start making a browser around this control.
the purpose of this lib is not really to compete with the IE ocx ,
it is only a lightweight alternative to it , if you need to display some tables and some formatted text and dont want to load a 16mb ocx into memory , you can use this lib.
//Roger
|
|
|
|
|
Hi,
I'm new to programming... so don't laugh too hard...
How do you run an Event Method (OnClick Button) from a void Method?
The Event Method requires the object and System.EventArgs variables?
How would you supply them from a none Event Method?
Also, I've noticed that I can run an Event Method from another Event Method my using:
btn_ClearTill_Click(sender, e);
Is this not a good idea?
Ron
|
|
|
|
|
myNameIsRon wrote:
How do you run an Event Method (onclick Button) from a void Method?
You can call an event handler, i assume you mean this by Event Method, from everywhere you want as long as you can access it.
myNameIsRon wrote:
The Event Method requires the object and System.EventArgs variables?
How would you supply them from a none Event Method?
As sender object you generally pass this and the EventArgs object has to be constructed.
btn_ClearTill_Click(this, new System.EventArgs());
myNameIsRon wrote:
Also, I've noticed that I can run an Event Method from another Event Method my using:
btn_ClearTill_Click(sender, e);
Is this not a good idea?
You can call an event handler from within another event handler, but it would be better to subscribe them both to the occuring event. This way both event handlers get automatically called when the event occurs.
www.troschuetz.de
|
|
|
|
|
Thanks Stefan,
I appreciate you help  )
Ron
|
|
|
|
|
Does anyone know if it's possible to have VS .NET 2003 check the DLLImport functions at compile time? FOr instance
<br />
class PlatformInvokeTest<br />
{<br />
[DllImport("C_DLL.dll")]<br />
public static extern void BridgeFn(lo);<br />
<br />
public static void Main() <br />
{<br />
try<br />
{<br />
string lo = string.Empty;<br />
BridgeFn(lo);<br />
}<br />
catch (Exception ex)<br />
{<br />
MessageBox.Show(ex.ToString());<br />
}<br />
}<br />
}<br />
While in my DLL There is no BridgeFn function that takes a string. This generates an error only on execution. While not horrible on a small scale, on a larger scale things can get pretty hairy pretty quick. If there is no way to check this at compile time any workflow suggestions to make this easier?
Thanks!
|
|
|
|
|
No, the compiler does not check these things (as you've found). Just make sure that the functions are exported from the DLL you're referencing.
As far as work flow, I really don't see why anyone would just "blindly" P/Invoke a function if they didn't know it was exported. Seems like a backward way of thinking. Typically, you P/Invoke a function because it's there, not vice versa.
If you want to see what exports are available, I recommend using depends.exe (the Dependency Walker) from the Platform SDK (installed by default with VS.NET).
Microsoft MVP, Visual C#
My Articles
|
|
|
|
|
Heath Stewart wrote:
As far as work flow, I really don't see why anyone would just "blindly" P/Invoke a function if they didn't know it was exported. Seems like a backward way of thinking. Typically, you P/Invoke a function because it's there, not vice versa.
Agreed, I don't know about you, but I have never written a program perfectly with out any mistakes before  I just wanted to avoid the case five months from now where I am trying to track down a bug and it turns out I was just passing the wrong data type in (Cause it seems like it doesn't do data type checking either) so guess that was my concern.
We basiclly have DLLs that we want to tie into because C# has such and easy way to design interfaces and that stuff. We have a lot of DLL's so it will be done on a fairly large scale.
|
|
|
|
|
But again, why would you P/Invoke a method before seeing if it either exists? That's like putting the cart before the horse.
Data-type checking isn't supported because you're marshaling to an unmanaged platform. C/C++ doesn't perform any type checking, either, except for what the compiler can perform at compile-time. In an unmanaged world, arguments and return values are only pointers on the stack (most usually). There would be no way to determine this using a managed compiler.
The best way to avoid errors is to truly understand the unmanaged and managed types, like that an unmanaged int is platform-dependent, i.e. 32 bits on a 32-bit processor and 64 bits on a 64-bit processor,thus you should use an IntPtr. A LONG is always 32 bits, hence is a managed Int32 (C#'s int primitive). A char* is a managed string (no ref or out) and should use CharSet.Ansi, where an LPTSTR is also a string but should use CharSet.Auto, etc. etc.
One thing to note is that currently in the .NET FCL Microsoft uses int where it should be an IntPtr because .NET 1.x does not support the 64-bit platform (it will in 2.0). I suspect they will either change to using IntPtr internally or maintain two different builds specifying an int for 32-bit platforms and a long for 64-bit platforms. I honestly don't know, but making your code use an IntPtr now will ensure that when it is compiled for the 2.0 framework and run on a 32- or 64-bit platform that it will work correctly.
Microsoft MVP, Visual C#
My Articles
|
|
|
|
|
Heath Stewart wrote:
But again, why would you P/Invoke a method before seeing if it either exists? That's like putting the cart before the horse.
So is there a way to do this in code? I am not the programmer writing the DLL's so while I'll try to keep my eye out the chances that something with the function (Data types etc) might change without me knowing right away.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
