Tag Info

Hot answers tagged

27

When both sides have good arguments and the opinions on the issue are too strong to come to a consensus, you as a manager need to make a decision and end the debate. Otherwise it will just turn in circles and fortify the positions of all participants even more. The longer you wait, the harder will it be for the "losing" side to admit defeat and work ...


19

Does the business value of implementing them exceed the cost? If you implement, you need to change not just your server, but all clients (although you can support both formats and only change clients as needed). That will take time and testing, which is a direct cost. And don't underestimate the time taken to really understand protocol buffers (especially ...


18

WCF shortcuts a whole lot of things in making a web service, but if you stray too far outside it's defaults you will have some additional work (usually configuration) to do that IMHO is not documented very well. Compared to ASMX services is can be a huge timesaver, but if you are writing REST services sometimes it is easier to use a MVC project as a ...


17

All those things are optional, use them if they're helpful, don't if they're not. It's as simple as that. You can certainly write good/proper web apps w/o any of those acronyms in your solution. Personally, I tend to find MVC to be a pretty lightweight and easy to use framework (much easier to get started on than webforms, imo). Likewise, LINQ provides ...


10

No, not really. LINQ is the greatest thing since sliced bread when interacting with a database. What you should remember is that these things are built on other things. LINQ is not adding to the number of things you need to know to develop an ASP.NET website, because now you don't need to know SQL. And LINQ is OO, which is far more in line with regular ...


10

User recoverable exceptions should not be "exceptions". Exceptions are for exceptional circumstances. Transposing a few letters in a form field is something that you should expect and plan for. Part of the impetus behind a "Service-Oriented Architecture" is that services are reusable. Sure, it might be a client sending messages to it... or it might be ...


10

i maintain apis and somebody before me added protobuf (because it was "faster"). The only thing faster is RTT because of of smaller payload, and that can be fixed with gzipped JSON. The part that is distasteful to me is the relative work to maintain protobuf (compared to JSON). I use java so we use Jackson object mapping for JSON. Adding to a response ...


10

Assuming both sides are 100% correct in all of their arguments, which ones matter? WCF models are not POCO, because of [DataContract] & [DataMember] and those attributes Do you care? Are you planing on doing something that requires POCO? WCF supports distributed transactions Again is this something you are going to use and need to build if ...


9

Ah yes...SOAP, the vaunted holy grail of computing. A lingua franca that promised interop between systems around the world. And then you get into the differences between SOAP implementations on Java and PHP and .NET. Or even between the WebSphere SOAP service and the Apache SOAP client. Never mind dealing with different WS-I compatability standards. Now ...


8

I should begin by saying that WCF is the goto solution. What you mentioned above fits very well in the SOA (Service Oriented Architecture) definition, and WCF deals very well with SOA. Implementing a single locking service application, which can then be then integrated in all your components would be ideal because: When you update your locking and payment ...


7

I hesitate to offer this up as an answer, since it's not exactly objective. But my personal experience is that every time I have been involved in a project that used WCF, we regretted it. If you are implementing something that genuinely makes use of WCF's flexibility (e.g. a SOA that needs to be accessed via HTTP/SOAP over the web and also via TCP over an ...


7

In answer to the 1st part of your question, I agree with your colleague's assessment that outputting JSON would be much more efficient & simple to do. (KISS principle) Before you go ahead with WCF though, I highly recommend that you consider the excellent Service Stack - an opensource .NET & Mono REST web services framework. The performance is ...


7

Using WCF has both advantages and disadvantages compared to direct socket programming. The main advantage is that you do not need to care about programming a server loop or communication protocol. You split your communication into function/method calls, include these functions/methods in your contract interface, create a class that implements it, ...


7

You are correct, in that in terms of how the code will change over time, I typically lean toward parameter wrappers so that later, when I need more information to perform the same function when adding a new feature, I can preserve signatures, and add one more property to the existing wrapper object. When it comes to building communication contracts like you ...


7

Put my two cents in. As a manager, you should ask your teammates to keep in mind the Yagni principle. This will help to reduce the list of reasons brought forward by both Teams. Our usage would be mostly for web, and we would expose our services over HTTP. In some cases (say 5 to 10 percent) we might need distributed transactions though. Rather ...


6

Just to follow-up and close out the post, with Preview 5, the WCF Web API took a huge leap forward making it incredibly simple to create REST APIs. And while the current codebase on Codeplex does not include a Silverlight client, there is a toolkit out there and I was able to easily strip out the Async-CTP parts from the open source code and create a SL ...


6

By reading your description I'm somehow afraid that one person simply cannot prepare satisfying documentation for such project unless developers already carefully comment their code by standard documentation comments. This is first step to allow new team members to use existing code base. Another step can be providing complex set of unit tests which will ...


6

So I would use the Adapter pattern here. Abstract the services to an interface that satisfies the needs of your app. And implement the details of that abstraction over the service. I would say this is a useful approach even if you're using one service because it helps avoid leaking the details of the underlying service into your application. For example, if ...


6

In my opinion, the strongest reason to become certified is that it gives you a built-in goal for helping you learn a set of technologies. Go for it, if only for that reason. Silverlight? Definitely. As mentioned in a couple of other answers here, and in my experience, it does not really differentiate a good developer from an also-ran. Experience and ...


6

I've done a lot of hiring for our company and to be honest, certs don't carry a lot of weight for us. If we see certs on a resume we'll make note of them, but just in passing. What we're looking for is experience. It doesn't have to be commercial experience (though that obviously carries more weight). Could be your own app using the technology, or even ...


6

By leveraging the Windows Communications Foundation framework, you can create services over a number of different network protocols. This includes HTTP, HTTPS, MSMQ, and even TCP/IP sockets. In addition to these, it also support Named Pipes for connections between two processes on the same machine. IIS can host applications developed for WCF, even if they ...


6

iPhone developers tend to prefer json or POX style services over SOAP. WCF is capable of serving both, though you might be better served by the WCF Web API than traditional WCF if you are going that way. Another option would be straight MVC controllers taking JSON or XML or HTTP POST data.


6

In my opinion, your observation is quite accurate. The high level implementations of XML based communication is usually not compatible with different platforms, even if they are both called "SOAP". Subtle differences in implementation, probably both within the scope of the standard implemented, create problems in real life use. My recommendation for service ...


6

They aren't a 1 for 1 replacement -- many times you'll use NServiceBus to feed messages into or take messages from a WCF endpoint. In any case, handling disconnected mode scenarios like this is where message queues really, really shine. NServiceBus is a good place to start. There are a number of other options out there. I'll note many of them do actually ...


6

I would do those in a different order- Firstly, I'd map my business domain, and figure out the best design to solve my business problem. This will give you your domain. Then, Ideally in a completely different mindset, think about the requirements of your client-side and UI; what data will be displayed, and how? This will give you your DTOs. ...


5

Nothing. You're still free to use WCF where it is most suitable, or at your own discretion. ASP.NET MVC has supported a RESTful communication style since its inception, and many people use it as a thin veneer for RESTful services. That doesn't automatically cause WCF to go obsolete, or make ASP.NET MVC the One Tool to Rule Them Allâ„¢. This is why ...


5

This isn't really a direct answer to your question, but an alternative for you to explore. In addition to my other answer, you can also check out another .NET web service framework called ServiceStack. Some good points about it: Open source. Support both SOAP and REST endpoints out of the box. Focus on performance, e.g. fastest text serializers in .NET, ...


4

It depends where you work. However if there are alot of candidates applying because the position is with a high profile company or the job is sort after, then expect to get eliminated early on from the pile of resumes if you don't have some certs in .NET. Personally I agree with the other answerers, but I think certs do play a role in giving you a certain ...


4

If the old concepts you mentioned didn't work any more, I would agree that would be mad, but the newer frameworks are alternatives. Blind acceptance would be mad. You need to justify. Personally, SQL in itself isn't a problem for me. Trying to add some of the functionality of modern websites, webforms isn't cutting it anymore. I'm sure some classic ASP ...



Only top voted, non community-wiki answers of a minimum length are eligible