Im running vb.net 2003.
Im still on a big learning curve with .net and like most people have great
ideas on what id like a peice of software to do.... but lack the knowledge
to do it
I have looked at the createwindowex function an have to admit ... im
baffled. What id like to do is run a function or proc that will pop up a
dialog box with a progress bar on and be able to pass values to the
progressbar, then distroy the dialog box after use. IS this possible using
the createwindowex function and if so how?
I know the easy route is to add a form to the project and a progress bar to
the form, but that i already know how to do
Thank you in advance for any help on this 8 1097
Peter,
I see using API calls forever as those who were in past addressing the
memory addresses which did reflect the monitor.
Using Net classes can mean that you with a new OS in future have the highest
chance not to come in trouble. They use maybe API's but that can be changed
for you on a new operating system.
The API is related with the OS so at the moment WIN32 for current Windows
Systems.
Therefore I try to avoid API's.
Cor
"Peter Newman" <Pe*********@discussions.microsoft.com> schreef in bericht
news:78**********************************@microsof t.com... Im running vb.net 2003.
Im still on a big learning curve with .net and like most people have great ideas on what id like a peice of software to do.... but lack the knowledge to do it
I have looked at the createwindowex function an have to admit ... im baffled. What id like to do is run a function or proc that will pop up a dialog box with a progress bar on and be able to pass values to the progressbar, then distroy the dialog box after use. IS this possible using the createwindowex function and if so how?
I know the easy route is to add a form to the project and a progress bar to the form, but that i already know how to do
Thank you in advance for any help on this
Cor,
As a novice at this really, i am open to all suggestions and opinions, and
lets face it i can learn more from people that have applied their ideas and
code than from a book
"Cor Ligthert [MVP]" wrote: Peter,
I see using API calls forever as those who were in past addressing the memory addresses which did reflect the monitor.
Using Net classes can mean that you with a new OS in future have the highest chance not to come in trouble. They use maybe API's but that can be changed for you on a new operating system.
The API is related with the OS so at the moment WIN32 for current Windows Systems.
Therefore I try to avoid API's.
Cor
"Peter Newman" <Pe*********@discussions.microsoft.com> schreef in bericht news:78**********************************@microsof t.com... Im running vb.net 2003.
Im still on a big learning curve with .net and like most people have great ideas on what id like a peice of software to do.... but lack the knowledge to do it
I have looked at the createwindowex function an have to admit ... im baffled. What id like to do is run a function or proc that will pop up a dialog box with a progress bar on and be able to pass values to the progressbar, then distroy the dialog box after use. IS this possible using the createwindowex function and if so how?
I know the easy route is to add a form to the project and a progress bar to the form, but that i already know how to do
Thank you in advance for any help on this
Peter,
I'm new at vb.net too, and am not an "expert" programmer anyway. But as
I understand it, vb.net encapsulates a lot of the old API calls into
the language, so you just don't need most of the API calls now -- the
various classes in vb.net, as organized in the various Namespaces,
perform the API calls for you.
An example is the API call "ShellExecute", which I used to have to use
a lot, and would include a Declare statement for it in my programs.
Now, you just call a vb.net command (I think its
System.Diagnostics.Process) which does all the work for you without you
having to "Declare" anything.
Good luck!
Peter Newman wrote: Cor,
As a novice at this really, i am open to all suggestions and opinions, and lets face it i can learn more from people that have applied their ideas and code than from a book
"Cor Ligthert [MVP]" wrote:
Peter,
I see using API calls forever as those who were in past addressing the memory addresses which did reflect the monitor.
Using Net classes can mean that you with a new OS in future have the highest chance not to come in trouble. They use maybe API's but that can be changed for you on a new operating system.
The API is related with the OS so at the moment WIN32 for current Windows Systems.
Therefore I try to avoid API's.
Cor
"Peter Newman" <Pe*********@discussions.microsoft.com> schreef in bericht news:78**********************************@microsof t.com... Im running vb.net 2003.
Im still on a big learning curve with .net and like most people have great ideas on what id like a peice of software to do.... but lack the knowledge to do it
I have looked at the createwindowex function an have to admit ... im baffled. What id like to do is run a function or proc that will pop up a dialog box with a progress bar on and be able to pass values to the progressbar, then distroy the dialog box after use. IS this possible using the createwindowex function and if so how?
I know the easy route is to add a form to the project and a progress bar to the form, but that i already know how to do
Thank you in advance for any help on this
Hello bo*@datasync.com,
I can't answer your question about CreateWindowEx(). I simply have never
used it. But to comment on the issue of .NET vs. Win32 API I have two thoughts:
First, learn the Win32 way of doing things so that you have the background
and knowledge to understand what VB/C#/.NET/et al is doing under the hood.
After you have that knowledge, don't ever use it if you don't have to.
ALWAYS, in production code, use the Framework equivalent. The reason being
is that .NET high-level language code is easier to read than Win32 P/Invoke
code. And as I have ranted about many times before, we write code for humans,
not for computers.
-Boo Peter,
I'm new at vb.net too, and am not an "expert" programmer anyway. But as I understand it, vb.net encapsulates a lot of the old API calls into the language, so you just don't need most of the API calls now -- the various classes in vb.net, as organized in the various Namespaces, perform the API calls for you.
An example is the API call "ShellExecute", which I used to have to use a lot, and would include a Declare statement for it in my programs. Now, you just call a vb.net command (I think its System.Diagnostics.Process) which does all the work for you without you having to "Declare" anything.
Good luck!
Peter Newman wrote:
Cor,
As a novice at this really, i am open to all suggestions and opinions, and lets face it i can learn more from people that have applied their ideas and code than from a book
"Cor Ligthert [MVP]" wrote:
Peter,
I see using API calls forever as those who were in past addressing the memory addresses which did reflect the monitor.
Using Net classes can mean that you with a new OS in future have the highest chance not to come in trouble. They use maybe API's but that can be changed for you on a new operating system.
The API is related with the OS so at the moment WIN32 for current Windows Systems.
Therefore I try to avoid API's.
Cor
"Peter Newman" <Pe*********@discussions.microsoft.com> schreef in bericht news:78**********************************@microsof t.com...
Im running vb.net 2003.
Im still on a big learning curve with .net and like most people have great ideas on what id like a peice of software to do.... but lack the knowledge to do it I have looked at the createwindowex function an have to admit ... im baffled. What id like to do is run a function or proc that will pop up a dialog box with a progress bar on and be able to pass values to the progressbar, then distroy the dialog box after use. IS this possible using the createwindowex function and if so how? I know the easy route is to add a form to the project and a progress bar to the form, but that i already know how to do Thank you in advance for any help on this
GhostInAK,
Would it than not be better following your advice to learn first WinFX
API's?.
I have seen to many OS's.
This is exactly why I don't agree with you your first part and completely
agree the last part of your message.
But just my opinion feel free to have yours.
Cor
"GhostInAK" <gh*******@gmail.com> schreef in bericht
news:be*************************@news.microsoft.co m... Hello bo*@datasync.com,
I can't answer your question about CreateWindowEx(). I simply have never used it. But to comment on the issue of .NET vs. Win32 API I have two thoughts:
First, learn the Win32 way of doing things so that you have the background and knowledge to understand what VB/C#/.NET/et al is doing under the hood. After you have that knowledge, don't ever use it if you don't have to. ALWAYS, in production code, use the Framework equivalent. The reason being is that .NET high-level language code is easier to read than Win32 P/Invoke code. And as I have ranted about many times before, we write code for humans, not for computers.
-Boo
Peter,
I'm new at vb.net too, and am not an "expert" programmer anyway. But as I understand it, vb.net encapsulates a lot of the old API calls into the language, so you just don't need most of the API calls now -- the various classes in vb.net, as organized in the various Namespaces, perform the API calls for you.
An example is the API call "ShellExecute", which I used to have to use a lot, and would include a Declare statement for it in my programs. Now, you just call a vb.net command (I think its System.Diagnostics.Process) which does all the work for you without you having to "Declare" anything.
Good luck!
Peter Newman wrote:
Cor,
As a novice at this really, i am open to all suggestions and opinions, and lets face it i can learn more from people that have applied their ideas and code than from a book
"Cor Ligthert [MVP]" wrote:
Peter,
I see using API calls forever as those who were in past addressing the memory addresses which did reflect the monitor.
Using Net classes can mean that you with a new OS in future have the highest chance not to come in trouble. They use maybe API's but that can be changed for you on a new operating system.
The API is related with the OS so at the moment WIN32 for current Windows Systems.
Therefore I try to avoid API's.
Cor
"Peter Newman" <Pe*********@discussions.microsoft.com> schreef in bericht news:78**********************************@microsof t.com...
> Im running vb.net 2003. > > Im still on a big learning curve with .net and like most people > have great > ideas on what id like a peice of software to do.... but lack the > knowledge > to do it > I have looked at the createwindowex function an have to admit ... > im > baffled. What id like to do is run a function or proc that will > pop up a > dialog box with a progress bar on and be able to pass values to the > progressbar, then distroy the dialog box after use. IS this > possible > using > the createwindowex function and if so how? > I know the easy route is to add a form to the project and a > progress bar > to > the form, but that i already know how to do > Thank you in advance for any help on this >
Good observations. In addition to recommending the framework version of a
API call for readability sake, the framework has checking it to avoid buffer
overflows and other type conversion issues that are easily overlooked when
calling the native API's directly.
Jim Wooley http://devauthority.com/blogs/jwooley/default.aspx Hello bo*@datasync.com,
I can't answer your question about CreateWindowEx(). I simply have never used it. But to comment on the issue of .NET vs. Win32 API I have two thoughts:
First, learn the Win32 way of doing things so that you have the background and knowledge to understand what VB/C#/.NET/et al is doing under the hood. After you have that knowledge, don't ever use it if you don't have to. ALWAYS, in production code, use the Framework equivalent. The reason being is that .NET high-level language code is easier to read than Win32 P/Invoke code. And as I have ranted about many times before, we write code for humans, not for computers.
-Boo
"Jim Wooley" <ji*************@hotmail.com> schrieb: Good observations. In addition to recommending the framework version of a API call for readability sake, the framework has checking it to avoid buffer overflows and other type conversion issues that are easily overlooked when calling the native API's directly.
Well, most of the .NET Framework's IO functionality is based on the Win32
API's file I/O functions too, so they could suffer from the problem too. I
don't see any disadvantages of a Win32 API-based solution that is used to
archieve things not exposed by the .NET Framework if it has been implemented
by somebody who is an expert in using the Win32 API from within .NET-based
projects.
--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://classicvb.org/petition/>
Herfried, Well, most of the .NET Framework's IO functionality is based on the Win32 API's file I/O functions too, so they could suffer from the problem too. I don't see any disadvantages of a Win32 API-based solution that is used to archieve things not exposed by the .NET Framework if it has been implemented by somebody who is an expert in using the Win32 API from within .NET-based projects.
I could have written it so unreadable is it.
:-)
However it did me remember those guys who were telling me all the time that
direct addressing the memory of the Dos monitor area was better than using
the API's for that.
:-)
Cor
"Herfried K. Wagner [MVP]" <hi***************@gmx.at> schreef in bericht
news:%2******************@TK2MSFTNGP03.phx.gbl... "Jim Wooley" <ji*************@hotmail.com> schrieb: Good observations. In addition to recommending the framework version of a API call for readability sake, the framework has checking it to avoid buffer overflows and other type conversion issues that are easily overlooked when calling the native API's directly.
Well, most of the .NET Framework's IO functionality is based on the Win32 API's file I/O functions too, so they could suffer from the problem too. I don't see any disadvantages of a Win32 API-based solution that is used to archieve things not exposed by the .NET Framework if it has been implemented by somebody who is an expert in using the Win32 API from within .NET-based projects.
-- M S Herfried K. Wagner M V P <URL:http://dotnet.mvps.org/> V B <URL:http://classicvb.org/petition/> This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics
by: todd |
last post by:
Im tring to learn about classes with php. I've read alot of posts here
and look at other peoples code. So I appied all the absorbed to this.
Im tring to build a Shopping cart. not for live use but...
|
by: CoolPint |
last post by:
I read that the return type has to be exactly same for a virtual
function to be overriden. While testing something, I discovered
something I cannot understand.
I cannot understand why the code...
|
by: Albretch |
last post by:
Hi,
client wants for a window with no toolbars to open (technical and
'esthetical' reasons) after the window, user clicks on, is being
closed.
I told them about security settings in browsers...
|
by: Dave |
last post by:
I used the following class and .aspx code below to understand how static
works on variables and methods taken from...
|
by: Eduardo78 |
last post by:
Ok, this is what i am tying to do:
I want to create a rutine that takes a value from a text box. Lets say for
example 5. and does the following 5*4*3*2*1 = 120
the rutine should be able to...
|
by: Sam Malone |
last post by:
I am trying to get details from a database. I really want to use only native
VS.NET managed code "stuff" (just cuz I want to) and avoid any interop
stuff. So, I'm trying to do this without using...
|
by: Frederick Gotham |
last post by:
I'm going to be using an acronym a lot in this post:
IINM = If I'm not mistaken
Let's say we've got translation units which are going to be compiled to
object files, and that these object...
|
by: BLUE |
last post by:
FirstClass members:
- static int counter;
- SingletonClass sc = SingletonClass.Instance;
Moreovere FirstClass uses a static class named SecondClass with a static
property...
|
by: akshaycjoshi |
last post by:
I am reading a book which says
Even though unboxed value types don't have a type object pointer, you can still call virtual
methods (such as Equals, GetHashCode, or ToString) inherited or...
|
by: taylorcarr |
last post by:
A Canon printer is a smart device known for being advanced, efficient, and reliable. It is designed for home, office, and hybrid workspace use and can also be used for a variety of purposes. However,...
|
by: Charles Arthur |
last post by:
How do i turn on java script on a villaon, callus and itel keypad mobile phone
|
by: aa123db |
last post by:
Variable and constants
Use var or let for variables and const fror constants.
Var foo ='bar';
Let foo ='bar';const baz ='bar';
Functions
function $name$ ($parameters$) {
}
...
|
by: ryjfgjl |
last post by:
If we have dozens or hundreds of excel to import into the database, if we use the excel import function provided by database editors such as navicat, it will be extremely tedious and time-consuming...
|
by: ryjfgjl |
last post by:
In our work, we often receive Excel tables with data in the same format. If we want to analyze these data, it can be difficult to analyze them because the data is spread across multiple Excel files...
|
by: nemocccc |
last post by:
hello, everyone, I want to develop a software for my android phone for daily needs, any suggestions?
|
by: Sonnysonu |
last post by:
This is the data of csv file
1 2 3
1 2 3
1 2 3
1 2 3
2 3
2 3
3
the lengths should be different i have to store the data by column-wise with in the specific length.
suppose the i have to...
|
by: Hystou |
last post by:
Most computers default to English, but sometimes we require a different language, especially when relocating. Forgot to request a specific language before your computer shipped? No problem! You can...
|
by: jinu1996 |
last post by:
In today's digital age, having a compelling online presence is paramount for businesses aiming to thrive in a competitive landscape. At the heart of this digital strategy lies an intricately woven...
| |