|
Hi All,
I want to zip a folder in C# without any third party dll. Can any body help me out.
Thanks,
Sunil G.
|
|
|
|
|
not sure what version of .Net but take a look at the following:
ZipPackage Class
hope it helps.
|
|
|
|
|
C# Zip Files and/or Folders[^] could help you out.
Too much of heaven can bring you underground
Heaven can always turn around
Too much of heaven, our life is all hell bound
Heaven, the kill that makes no sound
|
|
|
|
|
If you actually want to make a ZIP compatible file, I strongly recommend SharpZipLib. It's a third party DLL but so what? ... you are almost certainly already deploying more than one file, unless there is a really good reason not to use a library you should do so. It's free and doesn't have license restrictions that stop you using it.
|
|
|
|
|
The deflator in .NET is bad[^]. I can't think of any reason to use it, but maybe you have one. If you do, we can help you better if you share that reason.
|
|
|
|
|
Anyways I noticed how wrong my last code was so far.
// DECLARATIONS
// Declaring all my variables
const decimal SLICE_OF_PIZZA_AREA = 14.125M; //
const int diameter_12_16 = 8;
double diameterPizza;
double slicesPizza;
double area;
//INPUT
// Prompt for and get input from user
Console.Write("Please enter the diameter of your pizza:";
diameterPizza = Convert.ToInt32(Console.ReadLine()); // reads the line of text from the keyboard
// PROCESSING
if (diameterPizza >= diameter_12_and_16)
// END
// This allows the user to read what has been outputted then simply press any key to end.
Console.WriteLine("\n\nPress any key to end this application...");
Console.ReadKey();
That is the code I have so far the problem I am having with is these instructions and I feel really dumb, I am not able to understand what to do.
• Prompt the user to enter the diameter of a pizza in inches, that value will be implemented in the determination of the number of slices to cut that pizza into.
• Use a compound condition test to check that the diameter entered is within the range of 12” to 36” inclusive.
• When the diameter entered is good, determine the number of slices to cut the pizza in using an “if … else if” decision structure based on the following:
Diameters of 12” to < 16” cut in eight slices.
Diameters of 16” to < 24” cut in 12 slices.
Diameters of 24” to < 30” cut in 16 slices.
Diameters of 30” to 36” cut in 24 slices.
Calculate the area of the pizza in question, and then calculate the area of each slice.
Display the number of slices that should be cut from a pizza that size along with the area of each slice, formatted as shown in the sample output above.
• When the diameter entered is outside of the allowable range, display an appropriate error message.
• In either case, good or bad diameter entry, end the program when the user presses any key.
Sorry for the wall of text, anyways my next question is how do all this I have no idea. any hints would be great!!
|
|
|
|
|
It's basic maths, and can be done in a procedural manner, or better still by creating a class that contains the main functionality.
Consider this Pizza class that contains all the pizza related stuff, a Pizza instance can now be created and you just need to handle the UI stuff and the class will contain all the other info you need:
using System;
public class Pizza
{
public const int MaxDiameter = 36;
public const int MinDiameter = 12;
private int diameter;
public Pizza(int diameter)
{
if (diameter < MinDiameter || diameter > MaxDiameter)
throw new ArgumentOutOfRangeException(
"diameter",
string.Format(
"diameter must be between {0} and {1}",
MinDiameter, MaxDiameter));
this.diameter = diameter;
}
public double Area
{
get { return Math.PI * (Math.Pow((diameter / 2d), 2)); }
}
public int Diameter
{
get { return diameter; }
}
public double SliceArea
{
get { return Area / Slices; }
}
public int Slices
{
get
{
int slices;
if (diameter < 16)
slices = 8;
else if (diameter < 24)
slices = 12;
else if (diameter < 30)
slices = 16;
else
slices = 24;
return slices;
}
}
}
|
|
|
|
|
I don't mean to be rude but I don't believe that's how it is suppose to be done I believe I am suppose to make multiple constants then have multiple if and else if, I'm not sure how to do this though  if you could show me that way, would be much appreciated.
|
|
|
|
|
|
Okay then my mistake, I guess.
|
|
|
|
|
I agree, which is why I posted what I did - but didn't do his complete assignment!
It seems to be quite common to teach people to write spaghetti code and then introduce OOP which is probably what's happening in his case.
Personally, I see no reason why simple OOP shouldn't be introduced immediately but can see many reasons why not doing so is not great!
|
|
|
|
|
|
 5
|
|
|
|
|
Somehow I don't believe Hello World needed to be in OOP. You must crawl before you walk and walk before you run. If any of you say your first app you ever wrote was in OOP i'll call you a liar.
I've been programming for 25 years and and still don't know everything and find the more I know the more confused I seem to be. I'm certain he will learn OOP but there still is a need to teach elementary crap code techniques.
|
|
|
|
|
In C# it does, even if you gloss over it – an assembly consists of classes and your main method resides in a class. To write the output you need to call a method on an object (Console). OO really is that fundamental in C# (and Java too which is the other common course language).
|
|
|
|
|
Actually, I suppose I do see your point. In many ways I wish I were able to forget and learn from a more modern viewpoint. On the other hand there is something to be said for knowing alternative ways of approaching something even if it appears to be an old way.
|
|
|
|
|
Oh, I definitely agree. A computing course should introduce procedural, functional, OO, data/array based and declarative approaches, at least. Often you can think up a better solution if you have a full toolbox (though OO is a particularly versatile tool and even with just that you can do pretty well). But once you are concentrating on one language you should teach that in the way which is appropriate for that language, which is predominantly OO for C#.
|
|
|
|
|
DaveyM69 wrote: It seems to be quite common to teach people to write spaghetti code and then introduce OOP which is probably what's happening in his case.
Unless you have psychic powers, in which case you have already chosen not to read this reply  ...
This poster is a fresh newcomer to CP, and there's no indication he/she is learning OOP. I'd estimate a high probability this is homework, and a strong probability that he/she ... if learning anything beyond passing a course ... is learning "procedural" programming.
From an OO point of view, what is modeled in this scenario, imho, is not a 'pizza,' but a process which takes a pizza-spec as an input, and returns certain calculated data useful to the pizza-creator. If this were modeling a pizza, where are the toppings and cheese options ?
Your consistent use of Public properties as a substitute for methods/functions is interesting, but not a style of OO programming I would teach anyone.
imho people vary greatly in the extent to which they "take naturally" to OO programming, and, depending on the person, or group, developing the ability to write good solid procedural code in the classic get inputs => calculate => create outputs is a good foundation to build on.
In this case the OP actually has a pretty clear procedural pseudo-code outline of the solution. imho he/she needs help with implementation, not architecture.
I hope you take these comments as in the constructive spirit I intend ! On the one hand I applaud your effort and willingness to help the OP, on the other hand, I'm not sure you have provided anything but a quick fix.
best, Bill
"Use the word 'cybernetics,' Norbert, because nobody knows what it means. This will always put you at an advantage in arguments." Claude Shannon (Information Theory scientist): letter to Norbert Weiner of M.I.T., circa 1940
|
|
|
|
|
Anyone learning C# should be taught OO principles right from the start, as it's an OO language and you can't understand how to do anything beyond the trivial without getting it.
|
|
|
|
|
Good answer, I think your reasoning is spot on.
|
|
|
|
|
Hi Bill,
All comments are always welcome, whether in agreement or not. A sensible discussion of the different ways this can be approached can only be beneficial to the OP 
BillWoodruff wrote: From an OO point of view, what is modeled in this scenario, imho, is not a 'pizza,' but a process which takes a pizza-spec as an input, and returns certain calculated data useful to the pizza-creator
Hmm.. possibly but as we need to get more than one calculation (slices, area, area per slice) from just one specified diameter then an instance that is essentially a diameter wrapper makes more sense to me.
BillWoodruff wrote: our consistent use of Public properties as a substitute for methods/functions is interesting
You are quite correct, CalculateSlices() etc methods may be more 'normal'. Where the object is immutable, therefore the methods will always return the same value for a given instance, I always feel that properties are more suited. This is just a personal thing and I have never really thought about it - it's just what I do naturally in that situation.
BillWoodruff wrote: mho people vary greatly in the extent to which they "take naturally" to OO programming
Undoubtedly, but that normally stems from any pre-existing experience and/or the way they are initially taught. IMO there is no reason not to introduce very basic OOP from the outset rather than trying to lay it on afterwards.
|
|
|
|
|
Hi, I appreciate your thoughtful response !
I am reminded of many years ago when I created the first computer educational program for the French-American bi-lingual school in San Francisco (oh yeah, Apple II's, floppy disks, Logo ... and finally ... after a 'revolt' by parents ... I was forced to switch to Basic).
I had students from age eight- to sixteen+.
It fascinated me to observe that some children as early as age eight could easily understand the idea of recursion, and others, as old as sixteen, seemed to encounter the proverbial "brick wall" trying to "get it."
Years later, as an educator of adults, I observed similar differences in abilities of people to grok OO vs. procedural code, as well as recursion.
This thread is not the place to get into educational pedagogy, but I am a fan of Steven Pinker's (MIT) view of innate cognitive styles particularly as expressed in "The Blank Slate"[^].
While I do not believe a given person's innate cognitive styles are some 'fixed constellation' of traits, and I am a definite optimist about any individual's capability to change, I do believe that in terms of content and message, education does need to be informed by the idea "one size does not fit all."
By the way, I am a fan of George Spindler's (Stanford, retired long ago) work on discontinuities in the process of socialization as a stimulus to cognitive development.
On a practical level, this might mean that if I were designing an educational curriculum, I might have students learn some absolutely rigid strongly typed procedural language for six months, and then switch them to Lisp; and then, when they recovered from that, maybe Eiffel or F#
Please take all this with a large "grain of salt," since you are hearing from someone who started programming at age 41 after a lifetime in the liberal arts, academic social sciences, and psychotherapy ... and whose first language was 6809 assembly, followed by Lisp, and then ... PostScript
And now ... well ... to me .NET and C# are ... the best ... of all possible worlds.
best, Bill
"Use the word 'cybernetics,' Norbert, because nobody knows what it means. This will always put you at an advantage in arguments." Claude Shannon (Information Theory scientist): letter to Norbert Weiner of M.I.T., circa 1940
|
|
|
|
|
I rather agree with Davey on the use of properties here – when the values you want to read are uniquely specified by the current state of the object, and reading them has no side effects and does not require extensive processing*, a property is appropriate. As it happens, they are implemented as dynamic calculations, but logically those values are part of the state (you could set them when you modify the state, i.e. the diameter) and so querying them is querying the object state, which is what properties are for.
(*: This is one of those things that, in principle, shouldn't matter, but if you call a property getter you expect that to be almost free in terms of time, so it does. Also, as an aside, I once wrote an XML class which constructed the entire DOM tree when you assigned its Text property. I think that's probably abuse, although the rules for a property setter are more relaxed; setting a property can cause extensive recalculation and side effects such as data binding and screen refreshes.)
Toppings are not part of the problem space, the class could easily be extended to other facets of pizzas if they became relevant to the business case in future.
imho people vary greatly in the extent to which they "take naturally" to OO programming, and, depending on the person, or group, developing the ability to write good solid procedural code in the classic get inputs => calculate => create outputs is a good foundation to build on.
I disagree with you here. Procedural programming and OO programming are quite different in approach, and if you're learning an OO language (which almost everyone is and should be these days) you should be starting out down the OO road. Otherwise you end up with people writing procedural spaghetti, like half of what we see in Q&A. You need to know the language fundamentals (like flow of control statements which seems to be what the OP is learning at the moment) but the way in which you structure your approach to solving a problem is very important and needs to be introduced right at the start, in my opinion.
|
|
|
|
|
Hi Bob, Points well taken; I'm not on a jihad to keep Properties pure Although it's my 'style,' for whatever that's worth, to separate out methods and properties. And, for new students to OO, I think it's worth keeping them rather distinct ... at first.
I will comment that one way this problem as stated, is not 'real-world' is that in this scenario pizzas can vary in diameter.
In any actual 'pizza-prep' solution, there would be a finite set of baking pans of certain sizes and areas/slices could/should all be calculated in advance, and just returned by 'look-ups.'
When I look at QA questions, I see just as many OO equivalents to procedural spaghetti-code (... mmm ... what's the right moniker for that ?).
imho someone taught procedural coding in a structured, modern, style, and who internalizes/masters key principles like 'divide and conquer,' refactoring, and debugging, should not be 'tarred and feathered' with bugaboo accusations of spaghetti-witchcraft.
To focus back on pizza: I can see a procedural solution to the scenario here, but then a transition to an object model when the scenario is expanded to include multiple overlapping pizza-orders, and to deal with the problem of how to allocate the finite supply of baking pans, and the oven space, to optimize speed-of-delivery so pizzas with maximum profit margin are ready first This being the MOO approach (Machiavellian Object Oriented).
For some people whose innate cognitive styles make their plunge into OO difficult (see my remarks in response to DaveyM69 today), I think that learning procedural programming well gives them a sense of efficacy, and confidence, that then makes their transitioning to OO much easier.
best, Bill
"Use the word 'cybernetics,' Norbert, because nobody knows what it means. This will always put you at an advantage in arguments." Claude Shannon (Information Theory scientist): letter to Norbert Weiner of M.I.T., circa 1940
|
|
|
|
|
Nowhere in the instructions posted does it say anything about constants. The only possible constants are the Minimum and Maximum diameters.
The only place you are instructed to use if/else if is in determining the number of slices.
All the code in the class could be done in a procedural way instead (without the class) using a method level variable diameter obtained from the user input. Just use the code in the relavant property getters.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
