No customer has ever asked me this, but I would answer:
1. What's the alternative? I mean, you have a business need to publish the functionality of some component over the Internet, right? So, if not a Web Service, what would you use? COM+? No, this needs a trusted domain. A custom-made socket? Come on, what makes you think you'll ever code something better than IIS?
2. Web Services (WS) can run on top of any Web Server. WS is just a protocol for receiving/delivering XML over HTTP. It's platform agnostic. If you want, deploy a WS running on Apache or your favorite web server. There's even a module for Apache that allows you to run ASP.NET on it.
3. Your fear is only valid if you don't have a corporate web site. If so, you're already at risk.
4. You're putting a business component on the Internet. You better not trust anyone. You'll be open to attacks. That's a fact. If you have a trusted party and do not want to have all the Internet hassle, choose, e.g., a VPN and use your web server only internally.
Well, contrary to your experience, all my customers have raised issues not having any business logic or data on the IIS machine.
So my company had to settle with the following design for our Web based enterprise solution:
a. The ASP pages with only the display logic execute from the IIS.
b. They in turn call local COM components which act as clients to our Application Server sitting inside the firewall
c. The customers become happy because they think they have great control over the security of the system because they keep the IIS in DMZ and App server inside the firewall. They only allow a single particular port for communications between the IIS and the App Server.
d. This way if due to some IIS exploit a hacker gets control of the IIS machine he can only get to see the presentation logic sitting on the IIS. No business data.
I am aware about the WS theory and understand that they can run on top of any Web Server etc. I am however specifically asking the question in the Microsoft context.
So, what's the difference between your solution and creating a Web Service that does calls to your COM components?
No one said that you should put everything on the Web Server.
Again, Web Services are simply a standard protocol for receiving delivering XML messages. You can do Web Services in standard, old ASP, if you want to. You only won't have the automatic XML generated, but SOAP (the protocol used by web services) is very easy to generate by hand.
The benefit of our Developer Shared Hosting is that we try to be flexible to accommodate your requirements. While we offer disk-space, email and other standard features we are responsive to developer's needs.
I have created a COM object by wrappiing a .NET assembly using tlbexp. This assembly is dependent on another assembly which, in turn, is dependent on two third party assemblies (I can't rebuild them and give them "strong names"). How can I deploy these dependent assemblies (DLLs)so that the COM object will work?
I would be happy to deploy everything in the same directory. The problem is that I don't know which directory use. The main DLL (DLL_1), and the only one whose classes I wish to expose, has been registered by REGASM and is accessible to unmanaged code. Not being a "second generation" MS programmer, I don't know much about the registry -- except that the methods exposed by DLL_1 are visible using regedit -- but not DLL_1's physical location. I have placed copies of the other DLLs in various places (e.g. a) the bin directory of DLL_1's project and b) the directory that contains the copy of DLL_1 that was "REGASMed") without success.
Any help making up for my generation2 deficiencies (Gen 2 > DOS and < .NET) would be greatly appreciated.
By the way, do you think it will take ten years for Generation 2 to die? (I wrote DOS code in early 2003 and Generation 2 started in 1993).
I'm trying to simply print some text, along with one or more illustrations. The illustrations print fine, and the text does as well, as long as the font is huge.
I've tested this bug using sizes 73, 60, 50, 30, 20, and 10, and all sizes smaller than 50 appear as random characters. I've used both times new roman and Arial font families with identical results. Does anyone know why it is doing this?
I'm using C# in a windows forms application. Any Ideas?
I wrote an article for the same. But i forgot the discusson group where i kept that. but still i have that source which will help you to print your page and content while keeping the font size in mind.
Thanks, but my main issue has to do with beintg able to specify a particular font family and size without it appearing as gibberish. I don't need to worry about line spacing or anything like that. The text I'm printing is essentialy captions for a picture. The text displays perfectly at sizes of 50 points or higher, but immediately turns to random characters at smaller sizes.
Maybe I am just over fussy, but I would like to exactly replicate the OS Font when ownerdrawing a control. I have looked at the examples on CodeProject and the Web and all of them seem to fail to correctly render.
To demonstrate this try,
Create a new windows form application, and set the form to Tahoma.
Add a standard label, Textbox or other control, and set it to be FlatStyle=System. Set it's .Text to be "Debug"
Then add a new user control, override the OnPaint and Drawstring("Debug"...);
You will notice that the D and e have a different spacing and also that the final point of the e raises on the Drawstring text. (Use the XP magnifier or download the taskbar magnifier from MS powertools to see it more easily).
I have so far tried:
StringFormat, SmoothingMode, InterpolationMode and TextRenderingHint and yet I have failed to have much effect.
I am in the need to develop a .net component that can communicate two different sql server databases. These two servers are physically different location. That .net application will be in server A and it update some data into Server B located in some other place.
Can any one help me to develop database connectivity in either VB.net or C#.NET?
TVS Infotech Ltd
Last Visit: 31-Dec-99 18:00 Last Update: 5-Oct-22 9:26