This project is read-only.
1

Resolved

30-Minute Walkthrough - Page 5

description

The section "Define a New Version", item 6 says following:
 
  1. In the Name column for AddIntegerArray:1.0.0.0, change it to AddIntegers:1.1.0.0
    *Notice how the name AddIntegers:1.0.0.0 will show up as existing in the catalog. Because it already exists, you would not be able to import it with that name.
     
    Yet, when I modified it to AddIntegers:1.0.0.0, it did not throw error during import processing. However this particular operation was not added and there was no error message any where. Is the doco incorrect, are am I mistaken?

comments

williamo wrote Nov 20, 2007 at 9:27 PM

You already had AddIntegers:1.0.0.0 defined and you imported the same thing? It certainly wouldnt' be there because the service catalog for sure won't allow it, but it sounds like you found a workaround in the import tool that didn't raise the alert. Can you provide the exact steps you took to get this behavior so we can reproduce? Thanks.

rrudracodeplex wrote Nov 21, 2007 at 3:52 PM

Sorry, I may confused you.

I was simply following the document upto page 5 as stated. However instead of changing AddIntegerArray:1.0.0.0 to AddIntegers:1.1.0.0, I simply changed it to AddIntegers:1.0.0.0 (which is an existing operation). I was expecting to see an error. But it did not throw any error. However it did not add to the catalog because it already exists. This is the right thing to do. But I was expecting to see an error but there were none.

wrote Feb 25, 2009 at 3:59 PM

wrote Mar 3, 2009 at 4:25 PM

botto wrote Mar 3, 2009 at 4:26 PM

** Closed by botto 3/3/2009 8:25 AM

botto wrote Mar 3, 2009 at 4:26 PM

wrote Mar 3, 2009 at 4:27 PM

afromentin wrote Mar 9, 2009 at 9:22 PM

In the 30-Minute Walkthrough, page 6 section 10 :Double click the AddIntegers operation node in the administration tool to see both versions present.

I'm not able to see both versions but they both seem to be present as the wizard says when I try to re import the operation.
I had no problem with this step in the previous version (6.6.1.0)

wrote Feb 14, 2013 at 8:08 PM

wrote May 16, 2013 at 10:11 AM

wrote May 16, 2013 at 10:11 AM

wrote Jun 14, 2013 at 8:07 AM