-
I think classic need more love the current Diablo scripts aren't adapted for classic at all. can we do something about it?
Xirzz updated
4 years ago
-
```
Consider splitting all the AssemblyInfo.cs into a SharedInfo.cs and
AssemblyInfo.cs. The SharedInfo.cs would sit in a separate solution folder,
and physically in the root folder of the solution.
…
-
```
Consider splitting all the AssemblyInfo.cs into a SharedInfo.cs and
AssemblyInfo.cs. The SharedInfo.cs would sit in a separate solution folder,
and physically in the root folder of the solution.
…
-
```
Consider splitting all the AssemblyInfo.cs into a SharedInfo.cs and
AssemblyInfo.cs. The SharedInfo.cs would sit in a separate solution folder,
and physically in the root folder of the solution.
…
-
There are several thing that have to be done.
**Config.cs**
- ~~create config.ini at first start~~
- ~~methods to change the values in *.ini (therefore changes in the UI needed)~~
**Config.ini**
Se…
-
```
There is a problem in this case
private int ReadNextRow(Vdbe vm, DataTable table)
crashes on default case with a System.ArgumentException
Can't use
table.Columns[i].DataType = null;
columnVa…
-
```
The are subclasses that can be better in own .cs files.
Like a ProfileManager or the StaringContex
```
Original issue reported on code.google.com by `Tarion86` on 23 Feb 2009 at 2:43
-
```
There is a problem in this case
private int ReadNextRow(Vdbe vm, DataTable table)
crashes on default case with a System.ArgumentException
Can't use
table.Columns[i].DataType = null;
columnVa…
-
```
The are subclasses that can be better in own .cs files.
Like a ProfileManager or the StaringContex
```
Original issue reported on code.google.com by `Tarion86` on 23 Feb 2009 at 2:43
-
```
There is a problem in this case
private int ReadNextRow(Vdbe vm, DataTable table)
crashes on default case with a System.ArgumentException
Can't use
table.Columns[i].DataType = null;
columnVa…