Support

0 views
Skip to first unread message

emeshuris

unread,
Jun 17, 2008, 12:36:42 PM6/17/08
to OggSync Support
Hi,
Your product was going to be a star, but with the following, its not
looking so good?
I currently have 4 questions without a reply, its been over a week for
some.
I have posted questions and have added feature requests, no replies.
Being a .net developer myself, I can see that the most basic
programming practices are not followed.
Why not notify people that have purchased from you that there is an
update?

-Edward

OggSync Support

unread,
Jun 17, 2008, 12:52:16 PM6/17/08
to ogg...@googlegroups.com
Hi Edward,

We are still working on the beta, so it's not ready for a complete user base general upgrade so we have not announced it generally yet.

This is the community support forum, although we do our best to monitor and answer, the actual support email is sup...@oggsync.com.

I did a quick check of the forum here for questions you asked, and I only unanswered one I see was concerning missing sync folders in the configuration, which we haven't been able to reproduce, but it is on our list of things to look at once we have done the major work of porting the new photo sync and backup features to the mobile client.

Thanks - Shawn

Edward M. Meshuris

unread,
Jun 17, 2008, 4:17:55 PM6/17/08
to ogg...@googlegroups.com, sup...@oggsync.com
Hi,
It is really difficult to not get upset at this type of response:
1. If it is beta, then why is on your home page? Is it like google that never leaves beta?
2. Your website is confusing, it has support and contact us links, seemingly taking me to the same place. You delete items from the forum at will, which is horrible. And you have a link to a google group that is not the official place. Email support is probably the worst type of support IMO since I can not see if others have had this issue before.
3. You responded to one of my questions, ONE, its not on your site, and I was not notified of this response.
4. You are on version 4.20.x.x however your assembly is still 1.0.0.0, I have asked you about this, no response, how difficult would it be to open your huge solution, open the properties of the installer project and raise the version value?
5. I am really glad you obfuscated your code, it would be a very nice laugh indeed.

-Edward

OggSync Support

unread,
Jun 17, 2008, 5:03:05 PM6/17/08
to ogg...@googlegroups.com
Hi Edward,

Sorry you are upset.  Not my intention.  I will try to answer:

1. It's a public beta for those who want to try it out, perhaps we shouldn't put it on the home page, but it's what we choose to do.
2. Agreed the web site could use some cleaning up, we are a small company.  I did check our pending comments section and I did see your comments, they were never approved (along with most comments).  I will look at getting yours approved, we actually have a decent backlog (about 1000) of comments, we had to move to approving them as we had problems with spam/etc.
3. I think the confusion is you were posting to the web site.  We should probably remove the ability to comment there until we can get the bandwith to manage and approve the web site blog comments.
4. We do version our final assembly build (it's currently 4.20.3).  I'm not sure why you are seeing 1.0.0 unless it is related to the obfuscator.  I will look into that, but our main concern is keeping the installer working to correctly remove previous builds.
5. Low blow.

- Shawn

Edward M. Meshuris

unread,
Jun 17, 2008, 7:32:59 PM6/17/08
to ogg...@googlegroups.com
@#5 Sorry.
Not having ever used dotfuscator (if that is what you are using), I do not see why it would be changing the version of the assembly.
It seems that the actual application project is not getting its assembly information updated.

-Edward

OggSync Support

unread,
Jun 17, 2008, 7:40:56 PM6/17/08
to ogg...@googlegroups.com
Hmmm, you are right, we were only setting the version on the final setup project.  We will set it on that assembly as well next release.

Edward M. Meshuris

unread,
Jun 17, 2008, 7:49:26 PM6/17/08
to ogg...@googlegroups.com
cool beans.

-Edward

Edward M. Meshuris

unread,
Jun 17, 2008, 7:52:31 PM6/17/08
to ogg...@googlegroups.com
Since I am on a roll, there are still chunks of your code that are not obfuscated.
So I was able to see that you do use try catch, which is good, but you are missing the finally, which is where all that good memory release code could go...
this was related to the #5 comment....

-Edward
Reply all
Reply to author
Forward
0 new messages