>>In the WinForms project I am converting to Web Forms there is a Main Class (MainClass.cs) which is the entry point of the application.
>>In this class there are number of "public static string SomeName" properties declared (at the top of the class). Then the application sets the values of these properties based on user selection(s).
>>
>>In Web Forms there is a main page of the application but no main class (if I understand correctly). So I am thinking of creating a 'public sealed class' where to declare all these properties that WinForm MainClass declares.
>>Does it make sense? Or is there a better place?
>
>If the values are truly static (i.e. the same for all users) then a separate static class is probably the best way to go. Something like:
public static class Globals
> {
> public static readonly int MaxInt = 10;
> public static readonly string SomeString = "This is the string";
> }
The value is not static for all users but - maybe - for one user. For example, user selects a file he/she wants to work with. The original WinForms program then stores the name of this file into the MainClass. Then user changes the file that he/she wants to work with, and the value is updated. So it is not really static for all user; not even for the current user. But I think the current user program should be able to "get" this name from various other parts of the application (otherwise, I see no reason why the developer stores the value in MainClass). So I think I need something different than the Static Class (as you suggested).
Thank you for your help.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham