|
|
Definately the 'best of the best', thats my point exactly.....
A small community of Platinum / Golds members or maybe the editor could suggest a number of people to 'decide what would go in or not......'.
The code project site could have a dedicated area for managing the framework. The changes to the actual library would get votes / ammendments by the people above and
a quorum number would allow the code to become part of the library.
I don't know how other opensource projects work? Do you?
Charlie
|
|
|
|
|
|
The repository wouldn't be too bad. A simple start would be a discussion thread:
'CodeProject Framework'
and and an article containing the code. I'd put myself forward to manage the code side. Ofcourse having a namespace could mean that separate zones, ie strings, controls could be managed by different people. Code management is an arse but the benefits are great....
As to your other point, is there sarcasm present? I take you point though....There is one aspect to developing a public library.....lots of qudos when applying for jobs. If an applicant had that on his CV then it would almost guarentee him a job.
Creating a project would achieve the same thing as a library would evolve from that.
1) The application itslef.
2) A library of generic functions.
But what to do....?
Charlie
|
|
|
|
|
|
Yes....I know little of sourceforge, having literally just looked at it its seems the right thing to use.....
So who do we talk to about the possibility of taking this further?
Charlie
|
|
|
|
|
|
Hello everyone.
How can build an exe file by VS .NET to execute it on Windows_98?
Thank you
|
|
|
|
|
Please avoid to use VS.NET. It encompasses more than one compiler, and what you need to run an app differs a lot. Tell us what compiler you've used instead : VC7, VCMC++, VC#, ...
If you've made an app using the .NET run-time, then you've got to distribute this[^] as well.
|
|
|
|
|
I think what .S.Rod is saying is that your .NET app will run on Windows98 as long as it has the .NET framework installed on it. If it doesn't, then you have to include/install the redistributable framework, to which .S.Rod provides a link, in order to run your app.
You would be able to run Java apps without the Java runtime. .NET's CLR (Common Language Runtime) is quite similar.
hey. what? I didn't mean to say Java. Ouch, sorry. I won't do it again.
|
|
|
|
|
flipdoubt wrote:
your .NET app will run on Windows98 as long as it has the .NET framework installed on it
Yes, .NET apps run on Windows 98 provided the .NET run-time is installed.
There are limitations however : for instance, ASP.NET apps require IIS. Unfortunately, you can't install IIS on Windows 98. And it's not likely ASP.NET apps are able to run on PWS either, the light version of IIS tailored for Windows 98.
|
|
|
|
|
Would ASP not .NET have run on PWS? Either way, let's not quibble.
|
|
|
|
|
flipdoubt wrote:
Would ASP not .NET have run on PWS? Either way, let's not quibble.
On Win98, regular ASP 3.0 will run under PWS, however ASP.NET applications will need to be running under IIS.
Nick Parker
You see the Standards change. - Fellow co-worker
|
|
|
|
|
I create a setup project.
and it copy some file to the folder. if the file exist, I would like to backup it.
and will copy it back when uninstall.
how to do it?
thank you very much
chokchai chalermwattanatrai
|
|
|
|
|
Can anybody point me to a comprehensive list of all the Attributes build into the .NET Framework? Can anybody suggest a way that I can search the MSDN documentation for a comments on all the Attributes?
Because they are spread across so many namespaces, I find it difficult to get a good sense for all the Attributes out there. It's like you have to go at them from the context in which you're going to use them. I've read many articles on C# control design (here at CodeProject and elsewhere) that give me a glimpse of the properties that affect an object when viewed in the PropertyGrid, but that is just one small sub-set of the "built-in custom attributes".
What gives?
|
|
|
|
|
Default .NET attributes are in fact classes whose name is of the form ___Attribute . For instance [DllImport(...)] is managed by the DllImportAttribute class, in the System.Runtime.InteropServices namespace.
I am not aware of a flat listing of those attributes. However, you can use the * wildcard in MSDN to find all *Attribute classes.
|
|
|
|
|
Local MSDN: ms-help://MS.VSCC/MS.MSDNVS/cpref/html/frlrfsystemattributeclasshierarchy.htm
MS MSDN: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfsystemattributeclasshierarchy.asp?frame=true
|
|
|
|
|
|
Clickety police? Is this another bit of net lingo of which I am ignorant? Or are you talking about some kind of copyright violation for linking to a page within another site?
|
|
|
|
|
Clickety police is a funny name a lot of Cpians refer to when they make a url cliquable, with that top hat.
In fact, Chris has been handed a javascript code that automatically translates urls to full cliquable links, and it's expected to be used in the message board. But it isn't wired yet, obviously.
|
|
|
|
|
I am actually working on ASP. I wanted to learn/start with .NET. And the questions arises... where and how to start .net??
Any help...
I was born intelligent Education ruined me!.
|
|
|
|
|
asp.net[^].
Currently, the best ROI with .NET *is* ASP.NET
|
|
|
|
|
Thanks a LOT
I was born intelligent Education ruined me!.
|
|
|
|
|
OK, so what do I need to do, security wise, to allow this. I found that if you use the .net Wizards, you can manually add each assembly to the trusted assemblies collection, but I'd like to know how to do this via command line. Or, how do you get the .NET Setup Project created by Visual Studio to not include files, but rather, links to those files, and then have the setup program do the trusting to the users machine????
Thanks in advance.
Kyosa Jamie Nordmeyer - Cho Dan
Portland, Oregon, USA
|
|
|
|
|
Take a look here:
MSDN Clickety[^]
Paul Watson wrote:
"At the end of the day it is what you produce that counts, not how many doctorates you have on the wall."
George Carlin wrote:
"Don't sweat the petty things, and don't pet the sweaty things."
|
|
|
|