gusarov / metacreator Goto Github PK

What steps will reproduce the problem?
/*!
    using(var sr = new StreamReader("Types.txt"))
    {
        while(!sr.EndOfStream)
        {
            var typeName = sr.ReadLine();
            var type = Type.GetType(typeName);
*/
    public partial class /*= type.Name */Serializer : MySerializer</*= type.Name */>
    {

What is the expected output?
NullReferenceException in line
public partial class /*= type.Name

What do you see instead?
NullReferenceException in line *.meta.cs
Write( type.Name );

What steps will reproduce the problem?
1. Open any solution with MetaCreator inside SharpDevelop
2. Build
3. Error: $(SolutionDir)

-

Just like in BooLang

-

class Program
{
    int Method()
    {
        return 5;
    }

    /*!
    WriteLine("public override string ToString(){"
    WriteLine("return " + Program.Method() + ".ToString()");
    WriteLine("}"
    */
}


That can be done with double passes compilation with intermediate assembly. 
Just like WPF building.

research

Does we really need this? how about reusing current assembly references? How 
about including all namespaces for metacode?

GOAL:

    class Program
    {
        static void Main()
        {
            /*! for(int i=0;i<10;i++) { */

            Console.WriteLine(/*= i */);

            /*! } */
        }
    }

What steps will reproduce the problem?
1. Make double pass metacode
2. Use some class in 2nd pass from 1st pass

Ideally there should be no extra work to bring this in live.

VS and msbuild allows to use 'link' instead of 'add existing' cs file to 
project.
Lets work with this accurately

What steps will reproduce the problem?
1. Typed /*!*/ in metacode, for example to make in code space for metacode, but 
doesn't fill it
2. Compile 
3. Get error MetaCode: End-of-file found, '*/' expected 

What version of the product are you using? On what operating system?
1.4

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?


Please provide any additional information below.

Error   2   MetaCode: An assembly with the same identity 'mscorlib, 
Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' has already 
been imported. Try removing one of the duplicate 
references. C:\Users\Administrator\AppData\Local\Temp\MQuantity.meta.cs MtG.Doma
in

1) notify
2) object-downcast-dispatching problem
3) 'compiled at'

-

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


Please use labels and text to provide additional information.

Research, do we really need that?
Why WPF generates this?
Does MS DSL Tools generates this?

/*! dynamic q = 5; */

  CreditMaster.Service.Dal -> M:\WS3\Credit Master\Main\Source\Service\bin\CreditMaster.Service.Dal.dll
------ Rebuild All started: Project: CreditMaster.Service.Contract, 
Configuration: Debug Any CPU ------
  * MetaCreator.targets: Clean
  * MetaCreator.targets: Execute MetaCreator (Targets v1.6)...
  * MetaCreator.dll: Data\IDataService.tt - 38 macros processed. Evaluating...
  * MetaCreator.dll: Data\IDataService.tt - 38 macros processed to => 
  [Not changed]  Data\IDataService.g.cs

now it is allways '0'
calculate and use real line number.

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


Please use labels and text to provide additional information.

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


Please use labels and text to provide additional information.

MetaCreator utilizes separate AppDomain for compilation of macroses. But is you 
run msbuild or devenv on a builder as a separate process, there are no reason 
in separate AppDomain, because this process will exit just after build, and 
releases all temporary assemblies.

consider to use special property in targets or conditional compilation symbol

// <summary>
    /// Author: Salvatore Previti - 08-April-2009.
    /// 
    /// Visual studio host compiler keeps a cache of files during the MSBuild step, so they are not readed from disk.
    /// This is ok for performance and intellisense, right, but this introduces also some subtle bug!
    /// 
    /// See forum thread "Generated Code Not Building - VS Caching Problem?" at http://social.technet.microsoft.com/Forums/en-US/msbuild/thread/14bb304d-d8e6-4227-bc2b-e2e6d4f979be?ppud=4 for more informations.
    /// This task contains a simple but effective work around to this caching bug :)
    /// 
    /// How it works:
    /// 
    /// Visual studio keeps MSBuild Tasks dll loaded also between different compilations in the same appdomain where MSBuild is executed.
    /// Due to this fact, we can keep some states (static variables) between different compilations during the same development session.
    /// This class, infact, uses a static synclocked dictionary to keep states between different compilations.
    /// Each time static function UpdateFileUsageCount is called with the same prefix and with the same filename (case insensitive), the resulting value is incremented.
    /// 
    /// There is another "feature" (bug?) in visual studio cache mechanism... &lt;Compile Include="c:\test.cs"&gt and &lt;Compile Include="c:\test.cs "&gt
    /// are considered different files, so, they are cached as two different files (look the space character in "test.cs " in the second Compile tag).
    /// MSBuild and all filesystems, instead, treat both files as the same :)
    /// 
    /// So the solution! Each time we generate a file, we use a different number of spaces using our in-ram dictionary.
    /// The static function that does this is UpdateSpaces.
    /// During tests, a single space seems sufficient, but to be safe, I used MaxSpaces constant to use more than one space.
    /// 
    /// This system has some drawback, though:
    ///     1) You need to use this Task, so, you have to include a DLL and add some tags to your MSBuild project.
    ///     2) This should works for full pathed filenames.
    ///     3) Not garbage collector friendly - some objects (internal static dictionary and some Visual Studio cached files) will never be released and there is no way to release them.
    ///        This is a small amount of RAM, though, and should not be a problem during development.
    ///        During command-line MSBuild this problem can be ignored.
    /// </summary>

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


Please use labels and text to provide additional information.

-

1) MetaCode: Compile errors
/*! #error */

2) MetaCode: Evaluation exception
/*! throw null; */

3) Processed code compile errors
var q = /*= "unknown"+"variable" */ ;

ConsoleWriteLine("Now is ${DateTime.Now}.")
=>
ConsoleWriteLine("Now is " + DateTime.Now + ".")

or e.g.

var someLicalVariable = DateTime.Now;
ConsoleWriteLine("Now is ${someLicalVariable}.")

see [http://boo.codehaus.org/String+Interpolation BooLang]

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


Please use labels and text to provide additional information.

I should release V1.3

-

-

-

Both csc and metacreator tasks are ignored. Output is not updated.
This is expected behaviour from msbuild's point of view. But workatounds should 
exist. May be BuildAction=Meta? Or custom property for this item, like

<None Include="something.xml">
    <AffectsMetacode/>
</None>

1. Install into %programfiles%
2. GAC
3. NGEN
4. Register safe MetaCreator.targets for VS in HKLM
5. Extend Custom.Before.Microsoft.Common.targets

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


Please use labels and text to provide additional information.

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


Please use labels and text to provide additional information.

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


Please use labels and text to provide additional information.

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


Please use labels and text to provide additional information.

Research for security problems. Apply required restrictions to separate app 
domain.

-