VS 2005 SP1
-
I just find the HTML/CSS/JavaScript output curdles my eyeballs.
regards, Paul Watson Ireland & South Africa
Shog9 wrote:
I don't see it happening, at least not until it becomes pointless.
Telerik's control markup is pretty decent and compact (at least compared to guff like infragistics). Certainly good enough for LOB apps and website back ends with the advantage of not having to maintain complex cross browser scripting. If being super anal about markup I would avoid ASP .net controls all together (http://umbraco.org/[^], xslt and jquery is my favourite cocktail at the moment).
-
Telerik's control markup is pretty decent and compact (at least compared to guff like infragistics). Certainly good enough for LOB apps and website back ends with the advantage of not having to maintain complex cross browser scripting. If being super anal about markup I would avoid ASP .net controls all together (http://umbraco.org/[^], xslt and jquery is my favourite cocktail at the moment).
Ryan Roberts wrote:
(http://umbraco.org/\[^\], xslt and jquery is my favourite cocktail at the moment).
I don't do ASP.NET anymore but jquery is great, we use it for all our projects.
regards, Paul Watson Ireland & South Africa
Shog9 wrote:
I don't see it happening, at least not until it becomes pointless.
-
You probably have to update the manifests or something. Ain't .Net wonderful?
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001Manifest files are an utter disaster, I hate them with a passion. I have had apps that compile fine, but at runtime decide they can't find the dll, which is right there, and which has NO dependancies.
Christian Graus - Microsoft MVP - C++ Metal Musings - Rex and my new metal blog
-
You probably have to update the manifests or something. Ain't .Net wonderful?
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001Yea installer rebuild with the appropriate manifests is my bet.
Ant. I'm hard, yet soft.
I'm coloured, yet clear.
I'm fruity and sweet.
I'm jelly, what am I? Muse on it further, I shall return! - David Walliams (Little Britain) -
A colleague of mine installed it but I didn't. Last week we found out that when he compiled some ManagedC++ DLL on its computer they were not working on customer's computer (and on our VirtualPC test), whereas if I compiled them they worked. (it's a sort of System.IO.FileLoadException Exception from HRESULT: 0x800736B) I wonder if it's related.... I'm NOT going to install it....
The manifest generated by Visual C++ is updated to load the SP1 versions of the runtimes if SP1 is installed on the development computer. You need to install the SP1 versions of the runtimes on the end-user's computer to make it work. The appropriate merge modules should have been installed on his development computer; alternatively
vcredist_x86.exeshould also have been updated. The C/C++ runtime headers in SP1 and the compiler-generated code have presumably been tested with the SP1 runtime library, so you probably ought to keep them together. However, you can avoid auto-generated manifests by going to Project Properties, Linker, Manifest File, and setting Generate Manifest to No.Stability. What an interesting concept. -- Chris Maunder
-
Never seen a service pack quite like it. Its crazy how long it takes to install on a machine, and how much resource it uses. About as resource intensive as compressing a 1 hour video.
"Je pense, donc je mange." - Rene Descartes 1689 - Just before his mother put his tea on the table. Shameless Plug - Distributed Database Transactions in .NET using COM+
-
Never seen a service pack quite like it. Its crazy how long it takes to install on a machine, and how much resource it uses. About as resource intensive as compressing a 1 hour video.
"Je pense, donc je mange." - Rene Descartes 1689 - Just before his mother put his tea on the table. Shameless Plug - Distributed Database Transactions in .NET using COM+
i love that message at the start: "This may take several minutes or if you have more things installed it may take several hours." - that may not be the exact text. At the time i thought someone at MS had found a sense of humour. One hour later, the joke's on me; 9 minutes remaining. Russell
-
The manifest generated by Visual C++ is updated to load the SP1 versions of the runtimes if SP1 is installed on the development computer. You need to install the SP1 versions of the runtimes on the end-user's computer to make it work. The appropriate merge modules should have been installed on his development computer; alternatively
vcredist_x86.exeshould also have been updated. The C/C++ runtime headers in SP1 and the compiler-generated code have presumably been tested with the SP1 runtime library, so you probably ought to keep them together. However, you can avoid auto-generated manifests by going to Project Properties, Linker, Manifest File, and setting Generate Manifest to No.Stability. What an interesting concept. -- Chris Maunder
Mike Dimmick wrote:
The appropriate merge modules should have been installed on his development computer; alternatively vcredist_x86.exe should also have been updated
The thing is, I'm doing my installer with InnoSetup. I have no idea how to detect if these 'updated DLLs' are there or not (with pure C code BTW, as InnoSetup doesn't use .NET) and I don't feel like installing vcredist_x86.exe everytime, so I cannot really do it...
Mike Dimmick wrote:
The C/C++ runtime headers in SP1 and the compiler-generated code have presumably been tested with the SP1 runtime library, so you probably ought to keep them together. However, you can avoid auto-generated manifests by going to Project Properties, Linker, Manifest File, and setting Generate Manifest to No
I'm going to look a that, thanks!! :-D
-
The manifest generated by Visual C++ is updated to load the SP1 versions of the runtimes if SP1 is installed on the development computer. You need to install the SP1 versions of the runtimes on the end-user's computer to make it work. The appropriate merge modules should have been installed on his development computer; alternatively
vcredist_x86.exeshould also have been updated. The C/C++ runtime headers in SP1 and the compiler-generated code have presumably been tested with the SP1 runtime library, so you probably ought to keep them together. However, you can avoid auto-generated manifests by going to Project Properties, Linker, Manifest File, and setting Generate Manifest to No.Stability. What an interesting concept. -- Chris Maunder
Mike Dimmick wrote:
The C/C++ runtime headers in SP1 and the compiler-generated code have presumably been tested with the SP1 runtime library, so you probably ought to keep them together. However, you can avoid auto-generated manifests by going to Project Properties, Linker, Manifest File, and setting Generate Manifest to No.
If I do that it just doesn't run anymore :sigh: :( But that gave me an idea, maybe there is some hope with the "Allow Isolation" flag? ... testing ... build failed... well, I just have to NOT install VS SP1 and it runs...
-
Ryan Roberts wrote:
(http://umbraco.org/\[^\], xslt and jquery is my favourite cocktail at the moment).
I don't do ASP.NET anymore but jquery is great, we use it for all our projects.
regards, Paul Watson Ireland & South Africa
Shog9 wrote:
I don't see it happening, at least not until it becomes pointless.