michaeledgar / protobuf-net

Automatically exported from code.google.com/p/protobuf-net
0 stars 0 forks source link

Import .proto not successful with vb compile #77

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Define a "TestType" message and save in "test.proto"
2. In a new proto file, import "test.proto".
3. In the new proto file define a message and a field of type "TestType" 
as defined in "test.proto" and save the new proto file as "output.proto".
(The two proto files should be in same directory)
3. Run protogen from same directory as the two above .proto files: 
protogen -i:output.proto -o:output.vb -t:vb

What is the expected output? What do you see instead?
output.proto should compile successfully. Instead the following message is 
displayed: "Node not 
handled: /FileDescriptorSet/file/FileDescriptorProto/dependency/string"

What version of the product are you using? On what operating system?
1.0.0.262 on XP SP3

Please provide any additional information below.
This same procedure was successful when using protoc, producing C++ .h 
and .cpp files.  Please correspond with Mike at mike.adams21@gmail.com

Original issue reported on code.google.com by mike.ada...@gmail.com on 21 Sep 2009 at 3:57

Attachments:

GoogleCodeExporter commented 9 years ago
Additional info:
I tried the "-d" option and still the same result.

Original comment by mike.ada...@gmail.com on 21 Sep 2009 at 4:04

GoogleCodeExporter commented 9 years ago
Additional info:
The same procedue is also successful compiling into C# code.  VB just doesn't 
seem 
to work.

Original comment by mike.ada...@gmail.com on 21 Sep 2009 at 7:34

GoogleCodeExporter commented 9 years ago
OK; I will take a look. Sorry 'bout that.

Original comment by marc.gravell on 22 Sep 2009 at 5:11

GoogleCodeExporter commented 9 years ago
Fixed in source: http://code.google.com/p/protobuf-
net/source/browse/#svn/trunk/ProtoGen

To patch local install, copy vb.xslt over your local copy (if you have used the 
msi, 
then this should be in "%ProgramFiles%\protobuf-net\protobuf-net-VS9").

I will re-release the msi when I can; I'm on a new build (win7) at the moment, 
and 
don't have the right tools "to hand" to do this right now.

Also; strongly suggest that you use the "package SomeName;" line in the .proto; 
this 
makes life a lot more predictable when chaining .proto files.

Original comment by marc.gravell on 22 Sep 2009 at 6:03

GoogleCodeExporter commented 9 years ago
Thanks for the patch!!

Original comment by mike.ada...@gmail.com on 22 Sep 2009 at 1:23