We created several COM objects with ATL and VC++ 5.0. They have run
for a couple of years under our old Win2k IIS 5.0. Should they be
expected to work without revision in the newer asp.net?
Thanks in advance
"Scott"
news:9d2a1ec6-abb8-4846-b0f8-74e6008ed094@v29g2000hsf.google groups.com...
> We created several COM objects with ATL and VC++ 5.0. They have run
> for a couple of years under our old Win2k IIS 5.0. Should they be
> expected to work without revision in the newer asp.net?
>
http://www.aspheute.com/english/20000828.asp
the town, amongst young and old; a religious
disposition appears to be still maintained amongst our people, by their
holding frequent private religious meetings; and all sorts are generally
worshipping God at such meetings on Sabbath-nights, and in the evening
after our public lecture. Many children in the town still keep up such
meetings among themselves. I know of no one young person in the town who
has returned to former ways of looseness and extravagance in any
respect; but we still remain a reformed people, and God has evidently
made us a new people.
I cannot say that there has been no instance of any one person who has
conducted himself unworthily; nor am I so vain as to imagine that we
have not been mistaken in our good opinion concerning any; or that there
are none who pass amongst us for sheep, that are indeed wolves in
sheep's clothing; and who probably may, some time or other, discover
themselves by their fruits. We are not so pure, but that we have great
cause to be humbled and ashamed that we are so impure; nor so religious,
but that those who watch for our halting, may see things in us, whence
they may take occasion to reproach us and religion. But
not permit false miracles, or He will procure greater.
Jesus Christ has existed since the beginning of the world: this is more
impressive than all the miracles of Antichrist.
If in the same Church there should happen a miracle on the side of those in
error, men would be led into error. Schism is visible; a miracle is visible.
But schism is more a sign of error than a miracle is a sign of truth.
Therefore a miracle cannot lead into error.
But, apart from schism, error is not so obvious as a miracle is obvious.
Therefore a miracle could lead into error.
Ubi est Deus tuus?209 Miracles show Him, and are a light.
847. One of the anthems for Vespers at Christmas: Exortum est in tenebris
lumen rectis corde.[210]
848. If the compassion of God is so great that He instructs us to our
benefit, even when He hides Himself, what light ought we not to expect from
Him when He reveals Himself?
849. Will Est et non est.211 be received in faith itself as well as in
miracles? And if it is inseparable in the others...
When Saint Xavier works miracles. Saint Hilary. "Ye wretches, who oblige us
to speak of miracles."
Unjust judges, make not your own laws on the moment; judge by those which
are established, and by yourselves. Vae qui conditis leges iniquas.212
Miracles endless, false.
In order to weaken your adversaries, you disarm the whole Church.
"Mr. Arnold"
news:OVHPpsvVIHA.4440@TK2MSFTNGP06.phx.gbl...
>
> "Scott"
> news:9d2a1ec6-abb8-4846-b0f8-74e6008ed094@v29g2000hsf.google groups.com...
>> We created several COM objects with ATL and VC++ 5.0. They have run
>> for a couple of years under our old Win2k IIS 5.0. Should they be
>> expected to work without revision in the newer asp.net?
>>
> http://www.aspheute.com/english/20000828.asp
That article is rather old. In particular, it seems to have been written
before Visual Studio.NET was released. You can do most of what it talks
about by using the Add Reference command and using the COM tab to select
your installed COM component.
In addition, the article does not mention issues with threading (they may
not have been widely known in 2000, which I think was before .NET 1.0 Beta
1).
ASP.NET handles each request on a different thread pool thread. If two
requests arrive at the same time for pages that use your COM component, then
two instances of your component may be accessed simultaneously. This may
well work if you have no shared state between instances of the component.
However, if you haven't tested in a multi-threaded environment before (on
multiple-CPU systems), then this will be the first time your COM component
has seen such use, and it may be the first time it has the opportunity to
fail for that reason.
Also, beware of using a single instance of the component stored in Session
or Application state, or in static variables. In this case, the single
instance will be called from multiple threads, making it even more likely
that it will fail if it wasn't built for that.
--
------------------------------------------------------------ --------------------
John Saunders | MVP - Windows Server System - Connected System Developer