If Microsoft really wants this technology (.NET) to be accepted, why:
Can Microsoft not provide reasonable scripts/instructions for installing the software Everywhere I look, there are forums loaded with the same few questions:
1) What permissions do I need
2) What accounts do I have to modify
3) Why can I not log onto SQL (alias, "What is wrong with my connection string")
4) Where is (usually relates to a table or file that is stuck in some directory other than the one it needs to be located in)
While I realize XP, Server 2000 and Server 2003 are different, and SQL 2000/2005 are different....why can't Microsoft provide guidance That is only 6 major combinations.
And don't give me the stock answer that "all environments are different". If you look at the real world, allmost all the questions are the same half dozen or so
Also, it is not helpful to have forum moderators (.ASP , DotNetNuke, et all) who seem to think you have to jump thru "x" number of searches before the deem you worthy of an answer.
The incredible .NET mess
amienel
Sean,
My point is that you can have the best technology, but if you leave the users to waddle in the mud, the technology will never make it.
Whether it is the sample portals on ASPNET or the ones on DotNetNuke, or where ever, the technology provider has to make a commitment to help/assist those waddling in the mud. Otherwise the technology won't make it.
My issue with the framework is that it is there. Unfortunately, only there. Little, if any, practical detailed implementation examples, but lots of "PRESS RELEASE" examples.
Yet you would respond "there are plenty of online articles and KB entries". True, I am currently staring at more than 4" of articles/entries I have printed on ASPNET privileges. Each is accurate to its specialized topic, but the whole stack can't give you the guidance needed to build a functional application.
Everytime I hear someone say it's a IIS issue, SQL issue, XP issue, etc (and not my problem) it is clear to me they do not understand what it takes to make a technology grow. It's only when you solve the secondary IIS issue, SQL issue, XP issue, etc that you get an environment that allows the core technology to grow.
itmatters
1. To install the .NET framework requires Administrator priveleges.
2. None
3. That would be a SQL problem, not a .NET one.
4. I've never heard of this, and I've been working in .NET since the RC1 of .NET 1.0 came out.
It sounds to me that your gripes are with certain .NET applications, not with the framework itself. Therefore, I'd suggest you focus your ire on the developers of those apps and not with the developers of the framework.
asiu
Gary,
Although I can certainly say I have felt your pain, I also don't completely agree with your perspective. There is plenty of guidance out here...in fact maybe too much, which is the cause of so many searches.
All environments are different. : ) And what I mean by that is that mine works, but I know what my current settings are. I don't really know what your environment looks like right now and you haven't provided the specific details. Provide them here and I'll give it a try.
- Ryan
chriswillis
I must say that I don't experience any problems finding information about topics that interest me. I find the MSDN documentation to be brilliant, the MSDN magazine has numerous good examples and articles every month. The http://msdn.microsoft.com site is similarly useful. There are many, many .NET blogs that deal with a wide range of issues (I'm subscribed to over 50), and Google is a perennial resource.
The problem, as with all programming, is that there are so many permutations and possibilities that there is no one "right" answer. There cannot ever be a walkthrough as to how to build the application you want, so instead tools and guidance are provided to assist with various decisions. It's up to the developer to mold these various pieces of knowledge into a coherent whole.
In terms of the "secondary" issues, these cannot be automatically resolved for you, since they are issues that relate to the individual area. As an example, you can write your program so that it places log files in the Program Files folder, but Windows will simply not allow this for a normal user. The reasons for this relate to security issues, but you should not point to something like that as a failing of the .NET framework in general. It is a development tool, no more, no less.
That said the .NET team is working hard to try and resolve the impedance between .NET and things like SQL. An example is the LINQ project which will allow native access to databases, XML, and .NET collections, all using the exact same syntax, all strongly typed, and all with Intellisense.
Can you perhaps post some details of the specific problems you are experiencing I'm not too clued up on IIS and ASP.NET, but perhaps I can assis with any XP/SQL issues you are experiencing.