http://forum.prettyobjects.com/recent.aspx Pretty Objects Web Site - Recent Posts en-us http://blogs.law.harvard.edu/tech/rss Jitbit AspNetForum Fri, 10 Sep 2010 07:54:45 GMT Fri, 10 Sep 2010 07:54:45 GMT http://forum.prettyobjects.com/messages.aspx?TopicID=84

Thanks for your interest.


We plan to have a Visual Studio 2010 version of Visual T# soon (in october or november 2010), depending on the interest of other people and changes to make to our actual version.]]> Fri, 10 Sep 2010 07:54:45 GMT http://forum.prettyobjects.com/messages.aspx?TopicID=84 Fri, 10 Sep 2010 01:28:55 GMT http://forum.prettyobjects.com/messages.aspx?TopicID=83 ]]> Sat, 26 Jun 2010 08:21:31 GMT http://forum.prettyobjects.com/messages.aspx?TopicID=83

New features

• Use upper case letters to search for name within Intellisense (for example: Console.WL [Ctrl]+[Space] will show you WindowLength, WriteLine ...)
• Resources can now be integrated into T# projects
• New item templates are now organized into Categories
  

Improvements

• Project references are no more locked!
• Intellisense now displays less stuff (only what is expected to show!). But Project References are still loaded from disk, even for projects in the same solution!
• Code Completion for attributes does not add "Attribute" suffix
  

Bug Fixes

• Minor bug fixes, especially in Intellisense

Go to the download forum and enjoy testing!
edited by Ludovic Dubois on 23/06/2010]]> Wed, 23 Jun 2010 14:59:42 GMT http://forum.prettyobjects.com/messages.aspx?TopicID=82
If this is the first time you install a language (other than Visual Studio ones), you have to run ProjectAggregator2.msi too. You can run it before or after installing Visual T#.
If you are not sure if you need to install it, run it: it will stops if there is nothing to do.

Note that you need VS2008 SP1 for installing Visual T# in Visual Studio 2008.]]> Wed, 23 Jun 2010 14:57:20 GMT http://forum.prettyobjects.com/messages.aspx?TopicID=79 nightly builds are available?


I added resources in build 1107. Can you try it and tell me if it fixes your problem?


Thanks for making Visual T# better.]]> Fri, 28 May 2010 09:10:22 GMT http://forum.prettyobjects.com/messages.aspx?TopicID=79

I'm already working on it! ]]> Wed, 26 May 2010 15:32:04 GMT http://forum.prettyobjects.com/messages.aspx?TopicID=79 GOLD Parser System. Now this application generates a binary table file with symbols and DFA and LALR states, which must be read by my engine in the first step fr further processing. So even though the contents of the file is well defined, there's no way that I'm going to create a MemoryStream with that data in code without going through great pain (decoding Base64 would be the best approach I guess). So alone for the table file reader I have quite a number of tests which ensure that the file is correctly loaded and symbols are present as expected - which is why the very same stream is read and used for a large number of tests.]]> Wed, 26 May 2010 15:06:42 GMT http://forum.prettyobjects.com/messages.aspx?TopicID=81 TSHARP-147 ]]> Tue, 25 May 2010 09:46:06 GMT http://forum.prettyobjects.com/messages.aspx?TopicID=79
Otherwise, building cases in MemoryStream would be the best. Build exactly the case you want before runtest statement and test it...]]> Fri, 21 May 2010 16:34:15 GMT http://forum.prettyobjects.com/messages.aspx?TopicID=79


However, I wonder what your suggestion is for testing stuff which involves reading from files/streams? Embedded Resources just feel natural to me because they have no dependencies on external resources; the file cannot be locked or missing, and they're really part of the test code assembly.]]> Fri, 21 May 2010 09:41:54 GMT http://forum.prettyobjects.com/messages.aspx?TopicID=78 Fri, 21 May 2010 09:38:45 GMT http://forum.prettyobjects.com/messages.aspx?TopicID=80

testclass for Product
{
  test Product( string name, double price )
  {
    runtest Product p = new Product( "My Product", 123 );
    assert ...;
  }
}]]> Thu, 20 May 2010 12:40:32 GMT http://forum.prettyobjects.com/messages.aspx?TopicID=79
Thus, we will add it very soon.]]> Thu, 20 May 2010 12:36:05 GMT http://forum.prettyobjects.com/messages.aspx?TopicID=78 But I agree: the exception should not be thrown!


I just add it to our bugs tracker system: http://bugs.prettyobjects.com 
We will resolve it soon, you can watch the issue if you want.]]> Thu, 20 May 2010 12:34:33 GMT http://forum.prettyobjects.com/messages.aspx?TopicID=81
testclass for Product {
test Price set
when MinIncluded.BelowMinCase
{
... // code testing negative price
}

test Price set
{
runtest ValidatePriceSet( 0 );
runtest ValidatePriceSet( 10 );
}

test Price set
signature ValidatePriceSet( double val )
when MinIncluded.IsMin || MinIncluded.IsAboveMin
{
Product p = new Product( "T#", 100 );
runtest p.Price = val;
assert p.Price == val;
}
}



One minor issue was that the signature which requires a "void" before the method name. That was quickly fixed.




However, now the tests still fail, I get a NullReferenceException which I have no idea what causes it. The test output is not helpful in locating the error and the debugger doesn't give me more information either; the following is in the output:





A first chance exception of type 'System.ArgumentNullException' occurred in mscorlib.dll

A first chance exception of type 'System.NullReferenceException' occurred in TSharp.dll

A first chance exception of type 'System.NullReferenceException' occurred in TSharp.dll

A first chance exception of type 'System.Reflection.TargetInvocationException' occurred in mscorlib.dll




Here's my test code:



using System;
using System.IO;
using TSharp.Criteria;
using bsn.GoldParser.Grammar;

namespace bsn.GoldParserTest {
testclass for CompiledGrammar {
private CompiledGrammar grammar;

testcontext {
using (Stream stream = new FileStream(@"Z:\Test\TestGrammar.cgt", FileMode.Open)) {
grammar = CompiledGrammar.Load(stream);
}
runtest;
}

test TryGetSymbol(string symbolName, out Symbol)
when symbolName: ValidFormattedString.NullCase {
Symbol symbol;
bool result;
runtest result = grammar.TryGetSymbol(null, out symbol);
assert thrown ArgumentNullException;
}

test TryGetSymbol(string symbolName, out Symbol)
signature void ValidateTryGetSymbol(string symName)
when symbolName: ValidFormattedString.EmptyCase || ValidFormattedString.InvalidFormatCase {
Symbol symbol;
bool result;
runtest result = grammar.TryGetSymbol(symName, out symbol);
assert result == false;
assert symbol == null;
}

test TryGetSymbol(string symbolName, out Symbol) {
runtest ValidateTryGetSymbol(null);
runtest ValidateTryGetSymbol("invalid name");
}

test TryGetSymbol(string symbolName, out Symbol)
when symbolName: ValidFormattedString.IsValidFormat {
Symbol symbol;
bool result;
runtest result = grammar.TryGetSymbol("Integer", out symbol);
assert result == true;
assert symbol.Name == "Integer";
}
}
}

]]> Thu, 20 May 2010 11:03:37 GMT http://forum.prettyobjects.com/messages.aspx?TopicID=80 Thu, 20 May 2010 09:53:35 GMT http://forum.prettyobjects.com/messages.aspx?TopicID=79


Unfortunately, even after settings the file to "Embedded Resource" in the Project Explorer in Visual Studio, it is not embedded, which obviously leads to an invalid test (the testcontext step fails).]]> Thu, 20 May 2010 09:50:56 GMT http://forum.prettyobjects.com/messages.aspx?TopicID=78
I created a new test project with the following test (sorry for the formatting - does this forum support code blocks?):




using System;

using TSharp.Criteria;




namespace bsn.GoldParserTest

{

testclass

{

test

{

runtest 1=0;

}

}

}




I do know that it should be 1==0 instead of 1=0, but I didn't expect the compiler to throw a NullReferenceException:




Task "TSharpCompiler"

T# Compilation Task

C:\Program Files (x86)\MSBuild\Pretty Objects\TSharp\1.0\TSharp.targets(22,5): error : TSharpCompiler.Nodes.TSharpDebugException: Z:\Test\TestClass.ts(10,16): System.NullReferenceException: Object reference not set to an instance of an object. ---> System.NullReferenceException: Object reference not set to an instance of an object.

at TSharpCompiler.Nodes.Expressions.AssignmentExpression.get_HasSideEffects() in C:\TeamCity\buildAgent\work\f825465bfabafd8d\TSharpComp\TSharpCompiler\Nodes\Expressions\AssignmentExpression.cs:line 106

at TSharpCompiler.Nodes.Expressions.Expression.ValidateUsage(Statement currentStatement) in C:\TeamCity\buildAgent\work\f825465bfabafd8d\TSharpComp\TSharpCompiler\Nodes\Expressions\Expression.cs:line 564

at TSharpCompiler.Nodes.Expressions.AssignmentExpression.ValidateUsage(Statement currentStatement) in C:\TeamCity\buildAgent\work\f825465bfabafd8d\TSharpComp\TSharpCompiler\Nodes\Expressions\AssignmentExpression.cs:line 242

at TSharpCompiler.Nodes.Expressions.Expression.SafeValidateUsage(Statement currentStatement) in C:\TeamCity\buildAgent\work\f825465bfabafd8d\TSharpComp\TSharpCompiler\Nodes\Expressions\Expression.cs:line 545

--- End of inner exception stack trace ---

at TSharpCompiler.Nodes.Expressions.Expression.SafeValidateUsage(Statement currentStatement) in C:\TeamCity\buildAgent\work\f825465bfabafd8d\TSharpComp\TSharpCompiler\Nodes\Expressions\Expression.cs:line 557

at TSharpCompiler.Nodes.Statements.ExpressionStatement.ValidateUsage() in C:\TeamCity\buildAgent\work\f825465bfabafd8d\TSharpComp\TSharpCompiler\Nodes\Statements\ExpressionStatement.cs:line 76

at TSharpCompiler.Nodes.Statements.Statement.SafeValidateUsage() in C:\TeamCity\buildAgent\work\f825465bfabafd8d\TSharpComp\TSharpCompiler\Nodes\Statements\Statement.cs:line 388

at TSharpCompiler.TSharpSpecific.RuntestStatement.ValidateUsage() in C:\TeamCity\buildAgent\work\f825465bfabafd8d\TSharpComp\TSharpCompiler\TSharpSpecific\RuntestStatement.cs:line 211

at TSharpCompiler.Nodes.Statements.Statement.SafeValidateUsage() in C:\TeamCity\buildAgent\work\f825465bfabafd8d\TSharpComp\TSharpCompiler\Nodes\Statements\Statement.cs:line 388

at TSharpCompiler.Nodes.Statements.CompositeStatement.ValidateUsage(StatementStatus& otherStatus) in C:\TeamCity\buildAgent\work\f825465bfabafd8d\TSharpComp\TSharpCompiler\Nodes\Statements\CompositeStatement.cs:line 311

at TSharpCompiler.Nodes.Statements.TopLevelBlockStatement.ValidateUsage() in C:\TeamCity\buildAgent\work\f825465bfabafd8d\TSharpComp\TSharpCompiler\Nodes\Statements\TopLevelBlockStatement.cs:line 155

at TSharpCompiler.Nodes.Statements.Statement.SafeValidateUsage() in C:\TeamCity\buildAgent\work\f825465bfabafd8d\TSharpComp\TSharpCompiler\Nodes\Statements\Statement.cs:line 388

at TSharpCompiler.Nodes.CSI.MethodDeclaration.ValidateUsage() in C:\TeamCity\buildAgent\work\f825465bfabafd8d\TSharpComp\TSharpCompiler\Nodes\CSI\MethodDeclaration.cs:line 443

at TSharpCompiler.TSharpSpecific.TestMethodDeclaration.ValidateUsage() in C:\TeamCity\buildAgent\work\f825465bfabafd8d\TSharpComp\TSharpCompiler\TSharpSpecific\TestMethodDeclaration.cs:line 461

at TSharpCompiler.Nodes.CSI.CSIDeclaration.ValidateMemberUsage() in C:\TeamCity\buildAgent\work\f825465bfabafd8d\TSharpComp\TSharpCompiler\Nodes\CSI\CSIDeclaration.cs:line 2443

at TSharpCompiler.TSharpSpecific.TestClassDeclaration.ValidateUsage() in C:\TeamCity\buildAgent\work\f825465bfabafd8d\TSharpComp\TSharpCompiler\TSharpSpecific\TestClassDeclaration.cs:line 199

at TSharpCompiler.Compiler.TSCompiler.Compile(String projectPath, Program programToCompile, ICompilerStrategy strategy, Boolean reflectionOnly) in C:\TeamCity\buildAgent\work\f825465bfabafd8d\TSharpComp\TSharpCompiler\Compiler\TSCompiler.cs:line 224

at TSharp.MSBuild.Compiler.Compile(TaskLoggingHelper taskLogger, String projectPath, String[] constants, String[] sourceFiles, PEFileKinds targetKind, Boolean includeDebugInformation, String outputAssembly, IEnumerable assemblyFullNames, IEnumerable assemblyFileNames, String[] signatureFormats, String[] nameFormats) in C:\TeamCity\buildAgent\work\f825465bfabafd8d\TSharpComp\TSharp.MSBuild\Compiler.cs:line 67

Z:\Test\TestClass.ts(10,14): error TS400090: '1' cannot be written to]]> Thu, 20 May 2010 09:11:32 GMT http://forum.prettyobjects.com/messages.aspx?TopicID=77

New features

• Generate missing test skeleton from Tests Explorer case (drag missing case and drop it in source code)
• Select Tests Explorer test node and test case from source code (contextual menu: Visual T#|Select Test in Tests Explorer)
• Retrieve case from Test Explorer test node (contextual menu 'Goto Case')

Improvements

• Big refactoring for source and symbols management in Visual Studio (QuickInfo, Tool Tips, Code Completion, ClassView, DropDown, Tests Explorer...)

Bug Fixes

• Minor bug fixes, particularly in Tests Explorer, Tests Runner (for Working Space)

Go to the download forum and enjoy testing! ]]> Wed, 05 May 2010 22:45:56 GMT http://forum.prettyobjects.com/messages.aspx?TopicID=76 Live Tests Explorer to your source code! 

If this is the first time you install a language (other than Visual Studio ones), you have to run ProjectAggregator2.msi too. You can run it before or after installing Visual T#.
If you are not sure if you need to install it, run it: it will stops if there is nothing to do.

Note that you need VS2008 SP1 for installing Visual T# in Visual Studio 2008.]]> Wed, 05 May 2010 22:38:33 GMT http://forum.prettyobjects.com/messages.aspx?TopicID=75 New Features

• Live 'Visual T# Tests Explorer': manage actual and missing tests as soon as you write them!
  Access it from the Visual T# contextual menu
  

Improvements

• You can now stop test run from either Visual T# Contextual Menu or Test Explorer, when you run tests from either Contextual menu or Test Explorer.
  

Bug Fixes

• Minor bug fixes

Go to the download forum and enjoy testing! 

• 
  

]]> Fri, 16 Apr 2010 17:09:07 GMT http://forum.prettyobjects.com/messages.aspx?TopicID=74 unique Live Test Explorer window shows you actual and missing tests as you write them! 

If this is the first time you install a language (other than Visual Studio ones), you have to run ProjectAggregator2.msi too. You can run it before or after installing Visual T#.
If you are not sure if you need to install it, run it: it will stops if there is nothing to do.

Note that you need VS2008 SP1 for installing Visual T# in Visual Studio 2008.]]> Fri, 16 Apr 2010 17:00:54 GMT http://forum.prettyobjects.com/messages.aspx?TopicID=73 VisualTSharp


Have good tests :-)]]> Mon, 22 Mar 2010 09:08:19 GMT http://forum.prettyobjects.com/messages.aspx?TopicID=72

Go to the download forum]]> Tue, 02 Mar 2010 09:49:20 GMT http://forum.prettyobjects.com/messages.aspx?TopicID=71
If this is the first time you install a language (other than Visual Studio ones), you have to run ProjectAggregator2.msi too. You can run it before or after installing Visual T#.
If you are not sure if you need to install it, run it: it will stops if there is nothing to do.

Note that you need VS2008 SP1 for installing Visual T# in Visual Studio 2008.]]> Tue, 02 Mar 2010 09:41:15 GMT http://forum.prettyobjects.com/messages.aspx?TopicID=70
New features

• 'Go to definition' and 'Go to declaration' are implemented for symbols in the same project

Improvements

• Rewritten source and symbols management for Visual Studio (QuickInfo, Tool Tips, Code Completion, ClassView, DropDown...)
  
  • Far more efficient
  • Now works for current project (no more for external references only)

Bug Fixes

• Minor bug fixes for renderers from within Visual Studio

Go to the download forum]]> Thu, 18 Feb 2010 17:25:27 GMT http://forum.prettyobjects.com/messages.aspx?TopicID=69 UPGRAGE YOUR VISUAL T# to v1.8: a HUGE refactoring of Visual Studio integration code was made!

If this is the first time you install a language (other than Visual Studio ones), you have to run ProjectAggregator2.msi too. You can run it before or after installing Visual T#.
If you are not sure if you need to install it, run it: it will stops if there is nothing to do.

Note that you need VS2008 SP1 for installing Visual T# in Visual Studio 2008.]]> Thu, 18 Feb 2010 17:19:58 GMT http://forum.prettyobjects.com/messages.aspx?TopicID=61

All our extensions are available at: https://www.prettyobjects.com:7567/svn/public/TSharp/TSharpExtensions/


Particularly, Build Servers extensions are available at: https://www.prettyobjects.com:7567/svn/public/TSharp/TSharpExtensions/BuildServers/


You can browse the project directly from your browser to look at the code, but you should use a SVN client to directly access our source server.
We suggest you to use a tool  like Tortoise SVN (http://tortoisesvn.net/downloads) a free SVN client.


This way, you only have to update your root directory (directly from within your Windows Explorer) to be up-to-date! ]]> Sun, 10 Jan 2010 10:02:01 GMT http://forum.prettyobjects.com/messages.aspx?TopicID=61 Sun, 10 Jan 2010 02:38:48 GMT