C#

FirstPrevNext

Re: Making a single control as Windows Forms Control and Web Forms Control Judah Gabriel Himango20-Oct-03 5:23 Judah Gabriel Himango 20-Oct-03 5:23  As long as you use 5.5 or better, it'll work. And judging by the browsers used to access google in the past 2 years, it'll work for just about everyone. The graveyards are filled with indispensible men. Re: Making a single control as Windows Forms Control and Web Forms Control Heath Stewart20-Oct-03 5:24 Heath Stewart 20-Oct-03 5:24  It is possible - see my article on DevHood at http://www.devhood.com/Tutorials/tutorial_details.aspx?tutorial_id=388.   -----BEGIN GEEK CODE BLOCK----- Version: 3.21 GCS/G/MU d- s: a- C++++ UL@ P++(+++) L+(--) E--- W+++ N++ o+ K? w++++ O- M(+) V? PS-- PE Y++ PGP++ t++@ 5 X+++ R+@ tv+ b(-)>b++ DI++++ D+ G e++>+++ h---* r+++ y+++ -----END GEEK CODE BLOCK----- Re: Making a single control as Windows Forms Control and Web Forms Control Judah Gabriel Himango20-Oct-03 5:46 Judah Gabriel Himango 20-Oct-03 5:46  Very good article, Heath. I'm putting that one in my favorites. Any idea how to get around the SystemColors issue? The graveyards are filled with indispensible men. Re: Making a single control as Windows Forms Control and Web Forms Control Heath Stewart20-Oct-03 6:03 Heath Stewart 20-Oct-03 6:03  Nope. Even a reply in the same thread above ours was saying something about that. The control just refuses to use / understand it. If you want, though, colors can be passed as params in the control (even without coding, so long as the property is public and you pass an enum name from the SystemColors). I haven't tested this doing it with system colors, but it does work for web colors. I just know the control can't be initialized with system colors.   -----BEGIN GEEK CODE BLOCK----- Version: 3.21 GCS/G/MU d- s: a- C++++ UL@ P++(+++) L+(--) E--- W+++ N++ o+ K? w++++ O- M(+) V? PS-- PE Y++ PGP++ t++@ 5 X+++ R+@ tv+ b(-)>b++ DI++++ D+ G e++>+++ h---* r+++ y+++ -----END GEEK CODE BLOCK----- Re: Making a single control as Windows Forms Control and Web Forms Control Judah Gabriel Himango20-Oct-03 8:34 Judah Gabriel Himango 20-Oct-03 8:34  Yeah, you can even set the color of a control inside the class constructor without trouble. Figures, though. MS isn't really pushing this technology yet, maybe due to odd bugs like the SystemColor issue. The graveyards are filled with indispensible men. Re: Making a single control as Windows Forms Control and Web Forms Control Heath Stewart20-Oct-03 9:24 Heath Stewart 20-Oct-03 9:24  I wouldn't say that. They have mentioned it several times. This "technology" is nothing new or ground-breaking, though. .NET is essentially built on the fundamentals of COM, as it is a natural progression from COM (which is a natural progression from OLE). The ability to host the control comes from the CLR exposing the .NET control through a CCW, which is better developed by programmers to be scriptable (i.e., an automation server) and versioned correcly. I think you typically don't see these because embedded controls such as this are increasingly becoming stagnant and ill-used. When's the last time you saw an ActiveX control that was useful and not some spy- or ad-ware (like CometCursors)? I think they realize this. Besides, every application has specific requires. Most applications are either light-weight web applications or heavy-weight client applications (either installed or deployed over the network). Very few, I think, could be satisfied in such an HTML-embedded manner.   -----BEGIN GEEK CODE BLOCK----- Version: 3.21 GCS/G/MU d- s: a- C++++ UL@ P++(+++) L+(--) E--- W+++ N++ o+ K? w++++ O- M(+) V? PS-- PE Y++ PGP++ t++@ 5 X+++ R+@ tv+ b(-)>b++ DI++++ D+ G e++>+++ h---* r+++ y+++ -----END GEEK CODE BLOCK----- Re: Making a single control as Windows Forms Control and Web Forms Control igor196020-Oct-03 9:46 igor1960 20-Oct-03 9:46  When's the last time you saw an ActiveX control that was useful and not some spy- or ad-ware... Wrong: All what you see inside of yours IE is COM object exposed as HTML element. Yes, they are all windowless, but they are all COM controls. All plugable MIME types are resolved as COM objects too. ObjectBands, Toolbars and etc. are COM objects. MSFTs Automation Document architecture viewable inside IE is pure COM. Scriptable Hosts (VBScript, JavaScript and etc) -- COM. So, what are you talking about? Of course ActiveX controls are useful... "...Ability to type is not enough to become a Programmer. Unless you type in VB. But then again you have to type really fast..." Me Re: Making a single control as Windows Forms Control and Web Forms Control Heath Stewart20-Oct-03 10:31 Heath Stewart 20-Oct-03 10:31  Yeah, duh. I've been studying this stuff since OLE was early in its stages. The point I was making (read: intent of content) was ActiveX controls used in the content of HTML pages, like MSNBC's OLD navigation bar or the stock ticker control that you don't see much of anymore. I'm well aware of how IE is built and run, thank you. With DHTML and server-side processing being used much more for dynamic content these days, there is far less ActiveX controls and Java applets being embedded in a web page than before. At least with Java, you can be somewhat sure that a JVM is installed on a user's computer and the security model is more simplified (and perhaps not quite as good). With .NET, it's still early and not many people have it yet (especially, as we're seeing, the more cynical and paranoid corporate networks), and uses a much tigher control. You know how in .NET 1.1 that the Internet_Zone code group has at least SOME permissions? It was a lot of proof I presented to Microsoft via my MSDN Subscription accounts (and I probably wasn't the only one) that helped prompt that. Even the permissions they decided on don't let controls do much.   -----BEGIN GEEK CODE BLOCK----- Version: 3.21 GCS/G/MU d- s: a- C++++ UL@ P++(+++) L+(--) E--- W+++ N++ o+ K? w++++ O- M(+) V? PS-- PE Y++ PGP++ t++@ 5 X+++ R+@ tv+ b(-)>b++ DI++++ D+ G e++>+++ h---* r+++ y+++ -----END GEEK CODE BLOCK----- Re: Making a single control as Windows Forms Control and Web Forms Control igor196020-Oct-03 10:46 igor1960 20-Oct-03 10:46  It was a lot of proof I presented to Microsoft via my MSDN Subscription accounts (and I probably wasn't the only one) that helped prompt that. Even the permissions they decided on don't let controls do much. And so what? Your point was: that ActiveX controls are not used much anymore. Wishfull thinking: they are used alot and will be used for very long time. You are talking about security issues and etc. I'm talking about business: MSFT can start and stop support for anything at any time. What about you? What if you invested your time/resources/money into development of some very usefull ActiveX? And now this is your only source of income: you beleived in MSFTs hype about ActiveXs and you've done your part + your customers are pretty happy about your product... Now, if I correctly follow you: you are are one of many prompting MSFT to stop support of ActiveX inside IE? Is this true? So, what's your agenda here? And who are you to do that? Is this prompted by something else then trying to grab the market share? What is that? "...Ability to type is not enough to become a Programmer. Unless you type in VB. But then again you have to type really fast..." Me Re: Making a single control as Windows Forms Control and Web Forms Control Heath Stewart20-Oct-03 10:54 Heath Stewart 20-Oct-03 10:54  Can you read English? You're totally mis-reading my comments and putting words in my mouth. I was saying that I don't see near as many ActiveX controls embedded in a web page as there was even a short 2 years ago! Then, ActiveX controls (and Java applets) where all over the place. Java applets are still pretty oft-used, but it seems that fewer and fewer ActiveX controls embedded in HTML pages (I'll once again make the distinction, although you'll probably miss it a third time) are being used. I'm not against ActiveX. I use it often for a great many things, and I often needlessly expose my .NET controls for CCWs just in case I decide to interop them later. Where in the hell did you get that I oppose ActiveX? I'm merely making an observation based on countless sites that used to use ActiveX and now don't. And I'm not speaking solely about security issues. I'm speaking about - at what the original post was hinting - how embedded user controls are, perhaps, not pushed by Microsoft because 1) it is nothing new and is based on the fundamentals of COM, and 2) is often trouble-some because of the framework support and security, yes. ActiveX isn't sandboxed and uses only a couple constraints. .NET is far more picky and requires (typically) far more effort to "enable" on a client machine than what it's worth, especially when ultra-thin clients like web applications or thick clients like Windows applications are more effective.   -----BEGIN GEEK CODE BLOCK----- Version: 3.21 GCS/G/MU d- s: a- C++++ UL@ P++(+++) L+(--) E--- W+++ N++ o+ K? w++++ O- M(+) V? PS-- PE Y++ PGP++ t++@ 5 X+++ R+@ tv+ b(-)>b++ DI++++ D+ G e++>+++ h---* r+++ y+++ -----END GEEK CODE BLOCK----- Re: Making a single control as Windows Forms Control and Web Forms Control igor196020-Oct-03 11:00 igor1960 20-Oct-03 11:00  OK, thanx for clarification. Contrary, I see not less ActiveX controls embedded in a web page as I used to see them 2 years ago. However, I agree with latest MSFTs responce to Eola settlement, we may find less of them someday. But again, it just demonstrates my point of MSFT being able to stop/start anything at any time. Regards "...Ability to type is not enough to become a Programmer. Unless you type in VB. But then again you have to type really fast..." Me Re: Making a single control as Windows Forms Control and Web Forms Control Heath Stewart20-Oct-03 11:05 Heath Stewart 20-Oct-03 11:05  I don't think this will necessarily deminish the ActiveX controls we see now, such as Flash, Acrobat (Reader), QT, etc. (regardless of activation, i.e. in-place vs. MIME handler). I am hopeful that Microsoft (et. al., even some open-source players are backing them on this) will defeat EOLAS and perhaps take the prior-art argument mainstream once and for all. If not, users may be greatly annoyed by Microsoft's solution (among others), but the major ActiveX controls are still required for such content (at least for a few years to come - who knows what the future will hold).   -----BEGIN GEEK CODE BLOCK----- Version: 3.21 GCS/G/MU d- s: a- C++++ UL@ P++(+++) L+(--) E--- W+++ N++ o+ K? w++++ O- M(+) V? PS-- PE Y++ PGP++ t++@ 5 X+++ R+@ tv+ b(-)>b++ DI++++ D+ G e++>+++ h---* r+++ y+++ -----END GEEK CODE BLOCK----- Re: Making a single control as Windows Forms Control and Web Forms Control Judah Gabriel Himango20-Oct-03 11:13 Judah Gabriel Himango 20-Oct-03 11:13  But there are instances where html simply won't suffice as far as functionality or a rich UI. I think there are many instances where this technology could be applied. It's interesting you mention ActiveX being overly used as adware - I'm a big fan of Wildtangent 3d technology (which has heavily relied upon Java applets and ActiveX for years now), and the company has recently been the focus of a lot of privacy issues (they are getting better now though). It seems that companies can make a lot of money off of users' information, and ActiveX controls in the past have been a nice way to harvest that information. So your points there are very valid IMO. On that note, managed controls could address these issues in many ways. IE could prevent managed apps from doing certain things, such as launching other ActiveX controls (requires higher security clearance), doing file IO, etc. This could potentially prevent managed controls from being used as spyware - IE could limit or prevent the information the control has access to on the client machine. I think in the end this technology will be used mostly for streamlining the deployment process, not necessarily as an alternative to ASP.Net, though that idea has been thrown around inside MS. We'll have to see. That said, I wonder if managed DirectX 9 will run right in the browser...that'd be cool. The graveyards are filled with indispensible men. Re: Making a single control as Windows Forms Control and Web Forms Control Heath Stewart20-Oct-03 11:47 Heath Stewart 20-Oct-03 11:47  Actually, all this stuff is already controllable by the CLR (not IE). This means that the control accessed in any way (other than a custom host that doesn't abide by the rules) falls under the same restrictions (see .NET security permissions, policies, code groups, etc. for details). For instance, you could say that any control in the URL http://www.somedomain.com/* or http://www.somedomain.com/somesite/* can have certain IO control, control over the UI and clipboard, and much more (you can even customize these permissions that are used by the code in question but must be installed locally to be used during initialization of the CLR). This shouldn't be a function of IE, and, rightly so, it isn't. It's a function of the CLR - the very thing that "runs" .NET. That said, IE does enforce some control on ActiveX controls as of late (IE 5.0+). The control must implement certain interfaces and belong to certain COM categories to do certain things, but nothing even close to .NET or Java. IE's security control also gives you some control over what ActiveX can do, but it 1) isn't as restrictive, and 2) doesn't allow for as much "matching" as in .NET. For instance, you can say that signed ActiveX controls from a particular zone can do X, but unsigned ActiveX controls from the same zone can only do Y. And you get 4 zones from which you can choose. This further breaks down into safe ActiveX controls and unsafe ActiveX controls (those that implement those interfaces and catagories I mentioned before. All together, that's something like 4 zones * 2 signed states * 2 safe states = 16 possibilities (roughtly). In .NET, the possibilities are countless (even with the default membership conditions, since granular control is possible). As for DirectX, that would be kind of cool, but would probably be far too dangerous. SVG (if ever finished / widely adopted) does give you dynamic control over most basic things you can do with DirectX (such as object-oriented graphics, control, and some basic meshes(?)) and is fully scriptable (I think that's the part that's holding up the committee). You could, however, make a .NET embedded control that is a graphics surface with which you could use DirectX, should it be installed on the user's machine (but that's pretty much the case for anything like Flash, QT, etc., sans ActiveX itself on a Windows computer with IE 3.0+).   -----BEGIN GEEK CODE BLOCK----- Version: 3.21 GCS/G/MU d- s: a- C++++ UL@ P++(+++) L+(--) E--- W+++ N++ o+ K? w++++ O- M(+) V? PS-- PE Y++ PGP++ t++@ 5 X+++ R+@ tv+ b(-)>b++ DI++++ D+ G e++>+++ h---* r+++ y+++ -----END GEEK CODE BLOCK----- Re: Making a single control as Windows Forms Control and Web Forms Control igor196020-Oct-03 8:27 igor1960 20-Oct-03 8:27  I think a lot of responces here suggesting writing WinForm UserControl and hosting it inside IE are valid solution in having the same source base. However, the most important thing is not touched by those answers: WebForm Control usage doesn't require client to run .NET, while WinForm controls will require .NET runtimes installed on the client. "...Ability to type is not enough to become a Programmer. Unless you type in VB. But then again you have to type really fast..." Me Re: Making a single control as Windows Forms Control and Web Forms Control Judah Gabriel Himango20-Oct-03 8:30 Judah Gabriel Himango 20-Oct-03 8:30  True, good point. Fortunately .Net will be installed everywhere come 2005-2006. The graveyards are filled with indispensible men. Re: Making a single control as Windows Forms Control and Web Forms Control igor196020-Oct-03 8:45 igor1960 20-Oct-03 8:45  True, good point. Fortunately .Net will be installed everywhere come 2005-2006. ... And by that time as described in Avalon/Longhorn preview: Windows Form will be considered "legacy" .NET programs. "...Ability to type is not enough to become a Programmer. Unless you type in VB. But then again you have to type really fast..." Me Re: Making a single control as Windows Forms Control and Web Forms Control Judah Gabriel Himango20-Oct-03 11:15 Judah Gabriel Himango 20-Oct-03 11:15  Hahah how the years go by....I suppose by then we'll be running 3d rich GUIs in our Windows apps. Maybe we'll not even need programmers - we'll just tell the computer what to do. The graveyards are filled with indispensible men. Re: Making a single control as Windows Forms Control and Web Forms Control igor196020-Oct-03 11:18 igor1960 20-Oct-03 11:18  Maybe we'll not even need programmers - we'll just tell the computer what to do. ... Hope by that time computers will perfectly understand Chinese "...Ability to type is not enough to become a Programmer. Unless you type in VB. But then again you have to type really fast..." Me Clipboard and IStorage Oleksandr Kucherenko20-Oct-03 0:12 Oleksandr Kucherenko 20-Oct-03 0:12  Hi! Anybody know how to put IStorage or IStream interface into NET clipboard? (with example please) Good Luck Alex Kucherenko Re: Clipboard and IStorage Heath Stewart20-Oct-03 6:16 Heath Stewart 20-Oct-03 6:16  This really requires quite a bit of knowledge of OLE/COM. Remember that the .NET clipboard (and drag and drop functions) are just wrappers for their Win32 counterparts. The same stuff is possible, but in many cases you have to recreate some structs, enums, and interface definitions for stuff that is already in Win32. For example, the System.Runtime.InteropServices.UCOMISTream interface already exists, but an equivalent for IStorage does not. You'll have to create an interface with the proper GuidAttribute and interface methods (taking into account marshaling parameters). To do this correctly, you'll have to implement .NET's IDataObject yourself and recreate structures for FORMATETC and STGMEDIUM. .NET's IDataObject is created specifically for .NET, using objects instead of structs and interface pointers. You'll have to override it to make it work more like COM's IDataObject interface. After that, simply call Clipboard.SetDataObject(object) or Clipboard.SetDataObject(object,bool) in your client code. My recommendations, make your IDataObject implementation class take an object (perhaps of a specific type) and some other parameter to dictate whether the implementaiton itself should wrap it up in an IStorage or IStream object. So, I'm sorry there isn't example code like you asked, but this is actually a very big problem to solve and requires that you read-up on COM to understand it. Be sure to look at FORMATETC and STDMEDIUM. Both contains links to other material that should be helpful.   -----BEGIN GEEK CODE BLOCK----- Version: 3.21 GCS/G/MU d- s: a- C++++ UL@ P++(+++) L+(--) E--- W+++ N++ o+ K? w++++ O- M(+) V? PS-- PE Y++ PGP++ t++@ 5 X+++ R+@ tv+ b(-)>b++ DI++++ D+ G e++>+++ h---* r+++ y+++ -----END GEEK CODE BLOCK----- Re: Clipboard and IStorage Oleksandr Kucherenko20-Oct-03 21:09 Oleksandr Kucherenko 20-Oct-03 21:09  Hi! this is not realy what i want... I mae port of structures and interfaces long time ago, but I think I make something wrong... that is why I ask for example of code. BTW Heath Stewart wrote: After that, simply call Clipboard.SetDataObject(object) or Clipboard.SetDataObject(object,bool) in your client code. such code will not work with Clipboard implementation provided by NET Framework. That is why I need example with OleSetClipboard and OleGetClipboard API methods calls. Good Luck Alex Kucherenko Re: Clipboard and IStorage Heath Stewart21-Oct-03 3:01 Heath Stewart 21-Oct-03 3:01  Actually, such a call will work if you take something into account that I forgot to mention (sorry). If the data object implements System.Windows.Forms.UnsafeNativeMethods.IOleDataObject, it does work. Unfortunatel, it is a nested interface of an internal class, but the System.Windows.Forms.DataObject does. You can use reflection to set the FORMATETC and STGMEDIUM structs. Calling Clipboard.SetDataObject does, in fact, call OleSetClipboard. You should try downloading .NET Reflector and take a look at how Clipboard.SetDataObject is done. Like I said, everything you need is already there. You may have to use Reflection to do get at it or you could redefine your own structs and interfaces in the same way it does (except that your IOleDataObject won't be the same Type as theirs, but you can at least make your call to OleSetClipboard work the same). With that, I can understand how your interface methods aren't always correct. This happens often. I had a custom IClassFactory method with the same params. When I tried a trick where you write IDL, compile it with midl.exe to a typelib, then use tlbimp.exe to import that, the method had a mysterious third parameter. Using Reflector (that can disassemble in a much easier-to-follow way than ildasm.exe, and can also decompile), you can see how MS defined their interfaces and match them. Once you get your IOleDataObject interface defined correctly (remember, don't forget the GuidAttribute), you can pass the object directly into a correctly imported call to OleSetClipboard.   -----BEGIN GEEK CODE BLOCK----- Version: 3.21 GCS/G/MU d- s: a- C++++ UL@ P++(+++) L+(--) E--- W+++ N++ o+ K? w++++ O- M(+) V? PS-- PE Y++ PGP++ t++@ 5 X+++ R+@ tv+ b(-)>b++ DI++++ D+ G e++>+++ h---* r+++ y+++ -----END GEEK CODE BLOCK----- Remoting on .NET Framework 1.1 KC Ooi19-Oct-03 23:14 KC Ooi 19-Oct-03 23:14  I have download a few example on Remoting, but none could run on .NET Framework 1.1. How do I overcome the security settings. Re: Remoting on .NET Framework 1.1 Jeffry van de Vuurst20-Oct-03 1:51 Jeffry van de Vuurst 20-Oct-03 1:51  I think you need this: http://www.gotdotnet.com/team/changeinfo/Backwards1.0to1.1/default.aspx#00000153[^] HTH, Jeffry

Last Visit: 31-Dec-99 18:00     Last Update: 16-Jun-24 3:33 Refresh ᐊ Prev1...14447144481444914450144511445214453144541445514456 Next ᐅ

General    News    Suggestion    Question    Bug    Answer    Joke    Praise    Rant    Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.